[busterarm]

I'm seeing similar process but on large teams still finding this output to be unmaintainable.

The problem is that vanishingly few people actually understand the code and are asking the agents to do all of the interpretation and reasoning for them.

This code that you've built is only maintainable for as long as you are still around at the company to work on it -- it's essentially a codebase that you're the only domain expert in. That's not a good outcome for companies either.

My prediction is that the companies that learn this lesson are the ones that are going to stick around. LLMs won't be in wide use for features but for throwaway busy-work type problems that eat lots of human resources and can't be ignored.

[gck1]

I left my last company job just before "AI-first engineering" became mainstream, and you confirmed what I was feeling all this time - I have absolutely zero idea how teams actually manage to collaborate with LLM-managed projects. All the projects that I'm working now are my own and the only reason why I could do this is because I had unlimited time and unlimited freedom. There's no chance I would be able to do this in a team setting.

I'm positive that the last company's CEO probably mandates by now that nobody must write a single line of code by hand and there's likely some rigid process everyone has to follow.

Fun times ahead.

[busterarm]

I agree and commiserate. In the near term my picture is pretty grim. There's fantastic uses for these tools but they're being abused.

I was big on correctness, software safety (think medical devices, not memory) and formal proofs anyway, so I think I'm just going to take the pay cut and start selecting for those types of jobs. Your run of the mill SaaS or open source+commercial companies are all becoming a death march.

[bluefirebrand]

> Your run of the mill SaaS or open source+commercial companies are all becoming a death march.

Most of them already were death marches to begin with, now they are firing squads