Is it? It looks more like a forgettable moment to me. We're talking about an IPO, how many headline-making IPOs can you actually remember?
> as a SWE the gravy train is basically over in my view
That is not a result of the IPO even if you are right, and I have my doubts.
> they figured out how to make a program that does the job
No they figured out how to make software that makes the job easier. How is this any different from the introduction of optimizing compilers or type systems or any of the other software tools we all use? It makes programmers more productive, which means programmers can take on larger projects.
Coding agents have limits and the managers who forced their SWEs to use them are starting to figure that out. Using agents to both write code and review code sounds cool in theory but in practice it is not such a great idea -- it means that nobody actually understands the codebase and therefore nobody can actually debug the code when things break. No, you cannot just assume that you can also throw an agent at the problem when things break -- because the breakage might mean you lost access to the agent or the agent lost access to your system and cannot help you.
> difficult to grasp how much life will change in the coming years
Not too difficult to grasp. Shareholders will demand returns and Anthropic will have to deliver those returns. All the sky-high dreams about RSI and the next phase of human existence are going to evaporate and profit is going to be front and center.
Another possibility: Anthropic fails to survive the next recession and the companies that did not allow their employees to become dependent on Claude will be the winners.
As a 15 year old veteren in the systems programming space I have to disagree. You do not have to understand the codebase. You need to know the expectations and the invariants. Testing is also not the same as before, knowing how the system is supposed to behave is more than sufficient for 90 to 95 percent of the jobs. What you absolutely just cannot do is to not understand the design of the code that the AI writes, and still have instructions to make sure all the best practices in software and db design you have learn all along the way which too is readily available nowadays. A proper agentic workflow can do wonders in this regard.
Yes the code written are bloated but not necessarily runtime inefficient, but that's what most of the software jobs are about.
That seems highly unlikely, given that there are countless open-weights models available.
If nobody knows what your code does anymore, if it turns out that the tradeoffs AI makes metastacize over time, if it turns out that attention to detail ACTUALLY matters to the functioning of your systems (which it always has), then we are barreling for an extremely rude awakening. The water is just starting to move in the kettle - it might turn to a boil soon.
Maybe it’s helpful to draw a comparison to the textile profession.
Looms were great for the industry. It makes it possible to have a product that people know about and can want.
Automatic textile machines were great for the production of fabric but very bad for the professionals who were paid a salary to make it. More fabric could be made, but fewer people drew a salary from making it.
Similarly, compilers, type checkers and other standardization tools are great for the industry and allow more people to become SWEs. Automatic software generators, to the extent that they can do people’s job, will not be good SWEs.
All of that is true even if you dispute that Claude Code can do a SWE’s job today.
How would you become dependent on Claude? I'm certain they are trying their hardest at finding ways to lock you in, but at this point, there is no dependency.
AI workflows/skills/etc are independent of the model and company. Any comparable model will do.
Exactly...? This is the only one I'm sure to remember.
Netscape.
That was the big one. Launched everything. Not in reality, but in perception.