If there are 4500 years of developer work (not including "real work") it sounds like there are bigger problems.
The whole point of having developers do upgrades isn't just the manual work but so they learn and understand it. Skipping that isn't helpful.
And why would you wait until there's 4500 years of work before upgrading? Maybe the problem is that company policies need to be fixed rather than introducing AI.
If you have a backlog of 4500 “developer years” worth of upgrades, lack of AI wasn’t the problem, and making some attention nodes go brr cannot solve the root problem.
Java is a super verbose language, yet keeps getting written because “everyone knows java.” Has the cost of maintaining Java finally reached such critical mass that only an LLM can affordably maintain it?
I save a lot of work code generating the non-biz-logic parts of applications from simple declarative specs. I typically end up having to only hand code about 10% of the application.
12 comments
[ 23.9 ms ] story [ 2950 ms ] threadThe whole point of having developers do upgrades isn't just the manual work but so they learn and understand it. Skipping that isn't helpful.
And why would you wait until there's 4500 years of work before upgrading? Maybe the problem is that company policies need to be fixed rather than introducing AI.
I wrote an AI, oops, a shell script to handle such an upgrade decades ago.
Also
Imagine having to debug something that has 4500 years of lines of code.
Bezos could spend $41 million dollars a year since 2476BC or $112k a day (all without earning interest) , and he'll still have change.
Java is a super verbose language, yet keeps getting written because “everyone knows java.” Has the cost of maintaining Java finally reached such critical mass that only an LLM can affordably maintain it?
No AI required.