If they actually miss it they can call it back to work for triple the going rate.
They usually don't though. Those left behind have to figure it out again with whatever new tools they have at their disposal, thus continuing the great circle of corporate life.
Or corporate death if they don't figure it out in time and it is actually important. But even then, the management won't miss anything.
https://techtrenches.dev/p/the-west-forgot-how-to-make-thing...
(Has some AI tells though, probably AI-assisted?)
A lot of market forces tend to "naturally" create monopolies/oligopolies. For eg if you're the biggest steel plant you can operate efficiently and keep moderate margins, beating any plants not as big (economies of scale). An independent guy (or even the entire team) can't just open a new steel plant shop down the road, even if the current one sucks.
To be a bit honest, I'm a computational scientist who's never seen anything near 100K and likely never will. It's hard to imagine not having around 4 times my salary and not being able to start something myself.
I think your premise is significantly correct; things like launch HN (and even YC startups) are heavily software biased. I suspect you'll find about a hundred product hunt products for every physical kickstarter/indiegogo.
Even if you are good at those, for many companies, it's more about connections than about the ability to build stuff. So if you don't know the right people, it is very difficult to get a foothold.
Anyway in general, corporations are sticky. They save resources through scale and collaboration. Famously this is a problem for free market true believers because if you believe that the market is the most efficient mean of organizing people then you would expect firms to operate internally as free markets (or disappear). There is a whole body of work about it,
https://en.wikipedia.org/wiki/Theory_of_the_firm
In practice you can't just become your own boss and compete against firms.
Given I'm now in my mid-50s, things are looking grim. And I'm not getting paid SV silly money. I'm not even getting paid US dollers.
The biggest but not only example: https://en.wikipedia.org/wiki/Tom_Mueller (yes, lots of subcontractors involved, however, Nasa paid, with a bonus percentage provided by the US military)
Note that Mueller gives the payment situation at TRW, and the fact that he "wasn't appreciated" as a direct reason to go to SpaceX.
What did you think happened? Does anyone actually believe Musk did the technical design for that engine, just because he claims so? Or I should say he constantly claims it, staying slightly away from direct claims to avoid getting caught in lies (well ... getting caught AGAIN).
These people and bots have no idea what they are talking about. They’re parrots.
That’s great in theory, it rarely works in reality. Those people almost universally find new work quickly because they’re good, or retire because they can.
In both instances the idea of going back to bail out a company that just screwed you, operating with a giant target on your back when the inevitable next layoff occurs, isn’t worth it for 10x the salary. Ignoring the fact a business of any significant size isn’t approving paying someone to come back for 3x, they’ll just caN the manager for the fallout.
Hired as a code monkey, fired as a code monkey.
This is contextual on a number of factors. It seems difficult to establish in the general case.
Give the new people 6 months to benefit from all that institutional knowledge.
LLMs are a great tool, but more often than not it does show if the person using them knows what they're doing or not pretty clearly. Especially if it's anything larger than a trivial small change.
The problem is that "I copied the issue on claude code and then committed the code it produced" is not actually taking ownership.
> noone appreciates the years spent "googling and looking at stackoverflow" anymore, and frankly, they shouldn't be.
Well, I do, and I hard disagree with you there. If the human does not understand what the machine is producing, then I need a different human.
Having said that, and feeling more with you than the other guy, there is nothing for you to "disagree" with.
Mediocre was always buggy and broken in some ways, but for all intents and purposes it was good enough. Today somebody with a year of study can reasonably deploy something - for which the appearance of taking ownership and shipping a full stack of features has reached the bar of good enough.
Consider 10 years ago: Did you believe it was more likely that in the quality-distribution-of-software that we would, over time, create proportionally more quality? I dont think so and AI didn't meaningfully change the trend.
It changed the work dynamics, and still is changing, and with our inability to communicate is going to be an annoying mess.
Dont let the annoyances blind you to what LLMs can do for your point in space, or to where most of the points lie for the rest of the world.
I think we should care that our engineers have put the effort to understand the code they are responsible to produce. I don't care specifically about how they get that knowledge (I am using AI to learn myself, for example). But I disagree with the implicit assumption on the statement, which is, in my view, "humans don't need to understand the code any more" (because some fresh out of university might think they understand, but they really don't).
I can't work with that sort of surprise. I'm tuned to consistency, and I can work with consistently bad, but not with "95% absolutely amazing, 5% abysmal".
And I say this as someone who develops exclusively with LLMs now.
I am using Claude Code with Opus 4.5 and I have to correct it every day. It produces working code but it makes mistakes. The code is more verbose than it should be, misunderstands/ignores edge cases, etc. Daily.
And I am not a stellar world-class programmer. I am pretty average. I just read what it produces.