Hacker News new | past | comments | ask | show | jobs | submit
For a couple of year I have been reviewing code in my team and my job is only to review and coach other junior/intermediate members of the team - not to develop new features myself. The problem with AI is the merge requests now contain more code and often the chosen solution is overblown/overdesigned for what actually needs to be done.

With human coding, the lazyness of the developer and the urge to keep things simple and deliver faster often leads to simple solutions (with a time/effort/return tradeoff). With AI, I get overblown MRs that work, but oftentimes could be simpler (with said tradeoffs). So my work has become more difficult and time consuming, and the codebases grows faster. And I don't think my team members learn or grow at the same rate as they did before.

Now, I have no strong feelings against AI - it is just a tool afterall. And I have no experience what the long-term effects of this will be (just as anybody else).

>With human coding, the lazyness of the developer and the urge to keep things simple and deliver faster often leads to simple solutions (with a time/effort/return tradeoff).

I believe this will become one of the biggest tech debts generated right now. AI removes the pressure of inefficiencies and bad decisions across the board. There likely is even going to be a new equilibrium far worse than what we got today, only manageable by AI, but with "productivity" gains lost to inefficiency and complexity.

I don't see how any other outcome would be possible.

loading story #50546254
loading story #50545174
That's why I always optimize for as few lines of code as possible and for as much reusability of existing libraries as possible.

I think this is the ultimate benchmark for well written LLM generated code. DRY FTW.

loading story #50545550
Yeah this is my finding too. Sometimes it adds quite a bit that is only very marginally better.