florianherrengt

It means the company is measuring the wrong thing. I would much rather have someone on my team who ships less but whose work I can trust than someone much faster whose changes leave me wondering what …

Then I’m not sure what you mean by calling them a bottleneck. If the limiting factor is the rate at which experienced engineers can understand and validate changes, you have three options: generate le…

Corrupted or lost customer data, security vulnerabilities, incorrect financial transactions, regulatory breaches, production outages, irreversible migrations, important product change effectively impo…

Thanks for letting me know. I had no idea. I’ll follow up with the moderators.

The difficulty of producing code WAS one of the circuit breakers. We had tests, CI, code review, QA, architectural reviews, etc. None of those disappeared. But they were designed for a world where pro…

What you’ve described solves a different problem. You’ve put a lot of effort into making sure generated code conforms to your standards. That’s all good. But do the people still understand what the sy…

I tend to find that this perspective comes from people working on relatively small or isolated projects. On a large system, the customer being happy today isn’t enough. You need other engineers to be …

For the vast majority of 25K-line PRs, especially AI-generated ones, I would bet money that the person opening it does not actually understand all of it. If you genuinely understand the resulting syst…

They’ll care when nothing works, nobody seems able to fix it, building new features takes forever and every change breaks something somewhere else. This was already happening before. But now, a lot mo…

I do have a genuine question though: what value are you adding at that point? If you don’t understand the system, don’t know what the code is doing and you’re mostly prompting an LLM to make the decis…

I’m hardly a Luddite and you’re basically making my point. You’re deliberately constraining the output so changes stay small, human-reviewable and reversible. That’s good engineering culture. It isn’t…

This is extrapolating several steps beyond anything we actually know. Whether people will buy AI-generated software is a different question. The problem I’m describing already exists inside businesses…

Debt is debt. Some of it is absolutely worth taking on. I don’t have any issue with intentional debt when you understand the trade-off and have a clear payoff plan.

The industry doesn’t really owe people opportunities. Even if you think it should, that’s not how companies are going to behave.

If the people trying to understand the changes and guard quality are now considered the bottleneck, the answer isn’t that the reviewers need to move faster.

I wrote about this before. I don't think the vibecoders will have a job for a long time. At best, it will be minimum wage. See "AI Won't Take Your Job, Someone Using AI Will" > …

I use AI heavily, so this isn’t about refusing to change. You still have to understand the change yourself if you’re going to take responsibility for approving it. That work is fundamentally much slow…

Agreed. But it’s the difference between crashing at 30 km/h (19 mph) and crashing at 200 km/h (124 mph). AI massively increases the speed and scale at which bad engineers can do damage while…

The fact that a machine can do something better than humans doesn’t automatically make learning it pointless. We still teach arithmetic and algebra despite computers being vastly better at calculation…

I’d expect that layer of the industry to shrink substantially. Although, I don’t think immigration or country of origin is particularly relevant here. I never worked in the US but there are plenty of …

A manager isn’t normally the person deciding how the software should be architected or implemented. Their job is largely priorities, people, coordination and resource allocation. You are still an engi…

I tried to touch on that with this part: > Fixing it would require such a colossal amount of work that it would be impossible to even start justifying it to anyone in management. > And what are …

Nobody is getting paid significant money just to build a simple CRUD app. Even before AI. Companies pay experienced engineers because the supposedly simple CRUD sits inside a messy real system with ye…

I think that’s a completely different problem. I’ve worked with two junior devs recently who are very good precisely because they’re trying to understand what they’re doing, rather than just producing…