I do agree that a lot of engineers who want to do everything the old manual way are about to get really frustrated.
I don't think this is as universal as you say. There are a lot of engineers who are excited and happy to use these tools. Leave the bubbles of Hacker News, Lobsters, and similar sites and a lot of people are embracing these tools.
You also skipped the step where someone needs to direct the design. In the pre-LLM era it was commonly accepted that engineers who advanced to very senior roles would become less connected to the implementation details and more connected to steering, reviewing, and directing. Only a few years ago Hacker News was full of anecdotes about staff engineers who barely wrote code any more. Those people will have no problem switching to a new world where LLMs are handling implementation details.
Why people are so eager to surrender their birthright to the machines for the mess of pottage?
GPT-Company name brings together frontier AI models with Company's XYZ technology and domain expertise, enabling the specialized model [to] directly operate Company's tools. Engineers will delegate design objectives … with agents running tools, interpreting results, implementing changes, and iterating toward verified outcomes for engineer review.
We're WWW.hersheys.COM the fully Web integrated Global Information cocoa delivery company.
While I think SWEs(yeah, not HW/chip but that's not my field) are cooked in 5 years, I think we'll be quite busy in the meantime fixing all the bugs that AI finds.
Maybe that's the job of software engineering moving forward.
Client: Hey, we have got these 125 microservices created by our agents and for the last 25 days they got stuck and can't add any new feature without breaking things, can you take this?
Eng: Sure, lets sign a 24 month contract, my rate is 250$/hr
Client: Sounds good
I've been using Astra and Opus 5.5 all week and I still have to intervene and tell them to do something different all the time.
I think the people whose SWE jobs consisted of simple features, bug fixes, or tweaking .toml until the server works are on their way out.
Someone needs to steer the LLMs around for now, though. There is a very long tail of non-trivial work and expertise that can't yet be replaced by a CEO telling the LLM to make the product work. There are many CEOs trying to do that right now and, outside of very simple CRUD apps, it doesn't work yet.
Is average developer 100% the benchmarks ?
The challenge as I see it is in shifting checks further left, but actual mitigation is just not really an issue any more.
If costs go down enough,because of LLM's and possible manufacturing innovations, more chips will be designed, so maybe this will partially offset job loses.
So let's see.
This is HN mentality. But it is not how it always works. The first thought isn't we can make more money tomorrow by building more faster. It is we can make more money today by laying off all the people that we don't need now. Short-termism is the rule.
I wish this was hubris, but no. I would genuninely be happy to not have to do other people's work for them on top of mine.
Right. Because skills don't atrophy at all.
Not saying everyone is like this, but plenty enough are.
But hey, at least folks unburdened by the pressure to ship anything have plenty of time to play office politics.
https://ashutoshveriprajna.substack.com/p/ai-code-chip-bug-f...
Can't vouch for the source though.