HN user

grumpy_coder

112 karma
Posts0
Comments68
View on HN
No posts found.

Unfortunately were I live...

The sports clubs were bought out by private equity and charge large fees. The local park is rented to the same private sports teams 7 days a week. The local elementary closed it's playground. (been open for 40 years, installed gates 5 years ago) Only scouts at the church remains, and it has become oddly focussed on getting fairly rich kids into college.

The cuts include workers in senior director and vice president roles, as well as managers, product developers, product managers, program managers, software developers, site reliability developers, technical analysts, user experience developers and others.

They are in no-way laying off call center employees, they are laying off tens of thousands of the most highly paid US workers.

And yes the numbers of H1Bs granted in 2025 is relevant. You don't layoff 20% of your 100,000+ people workforce all of a sudden 'cos March went badly.

Yeah, I think the first mistake is thinking 'large software project' is specific enough to have any good advice at all.

Large software projects could include AAA console videogame, or banking mobile app, or embedded vehicle entertainment system, or airport baggage handling system, or hundreds of other totally different domains.

The only good advice I can think of is given a large software project try to hire someone (or a whole team) that have built something pretty similar before.

The grocery bagger on a zero hour contract needs to be able to survive when not given 40 hours. Also the 5% unemployed people in a 'full employment' economy need to be able to survive when sacrificed to control inflation.

Boeing has consistently underperformed the market massively since the MD merger. Making maybe 3% after inflation

Monorepo very often means bazel for tooling (rbe and caching tests) and that means one WORKSPACE with common versions of libs.

Monorepo also means a team 'vetting' new thirdparty libs, and a team telling you your CI takes too long, and a team telling you to upgrade your lib within 23 minutes because theres a security issue in the korean language support...

Should managers exist?

We got along better before all these managers arrived, could ship huge projects with 100 people and one ceo. And the ceo wrote code and didn't do any of the nonsense most managers fill their days with.

This sounds far more real to me than the original post. All the technical issues in the world don't bother me unduly, it really is the managers who make you hate work.

Money wise these corps are a system of their own, they pay enough to make you not quit. The more they pay, generally the more they suck.

Just need to wait till my 401k doubles one more time, my kids finish college, and the house is paid off.... just 10 more years

I believe the conclusion is correct in 2025, but the article in a way just perpetuates the 'misinformation', making it seem like finding if your code will compile to a dynamic branch or not is easier than it is.

The unfortunate truth with shaders is that they are compiled by the users machine at the point of use. So compiling it on just your machine isn't nearly good enough. NVIDIA pricing means large numbers of customers are running 10 year old hardware. Depending on target market you might even want the code to run on 10 year old integrated graphics.

Does 10 year old integrated graphics across the range of drivers people actually have running prefer conditional moves over more arithmetic ops.. probably, but I would want to keep both versions around and test on real user hardware if this shader was used a lot.

"it will almost certainly double in value in 7 years" implies 10% is an almost certain long term return. It is not.

10 years is a common rule of thumb to double your investment, this is a good guess since after adjusting for inflation, the real return of S&P 500 is about 6.8%. Which is about 10.5 years to double your investment.

(give or take S&P 500 being one of the best returns you will find historically)

I see an over-reliance on automated tests recently. Often suggesting just passing the CI tests is enough to approve a change. In ancient code it's just as important to limit the blast radius of your changes, and have a good reason for making them. Not changing something is the ultimate way to prevent a regression.

It's also important to realize claim denial isn't the same for all customers. When I was classed as an executive at a large blue chip company, my claims were approved quickly and easily at the company specific hotline. With the same provider, making the same claims, they are now partially denied initially and it requires long phone calls to get them to admit they should be covered and often it just isn't worth the hassle.

100% this; unfortunately also often seeing junior devs called staff after job hopping for 3 or 4 years never really learning anything.

Junior job titles are nearly as much of a mess as interviewing them.

Particularly in recent hot topics like AI the reality is you want both experienced and less-experienced devs. Most AI teams I see actually lack AI experience and keep falling for the same issues (like quickly getting to 80% working and thinking just a bit more data to 99.9%)

"Instead of using typical supercomputer networking solutions like Infiniband, Tesla chose to adapt Ethernet to their needs with a modified transport layer."

So, they need to compare it to Infiniband, not TCP, and definitely not software TCP. And they need to explain how/if it works with standard huge capacity switches (which is at least a reason to prefer TCP over Infiniband).

There could be reasons to build this, AWS have something, but for Tesla to build their own stinks of NIH bad.

Generally, nobody has authority. Even the highest executive has to fight procurement in a big corp. Own a VC-backed startup, the investors want you to get prior agreement on 'large' purchases. Maybe if you are the sole owner of a small firm without a purchasing department.

Politics always has people insert themselves in the flow of money.

All hit-driven industries, TV, movies, toys, games, anime, etc... need to be forced to pay the people who make them royalties. Money is always tight most of the time, but when someone makes a hit they need legal protection to a fair share of the huge profits.