But that is fundamentally what agile is about. It's not about coding faster, it's the recognition that the specs are incomplete or wrong because fundamentally, a lot of customers cannot tell you what the want until they see it. That's why "build something simple and iterate on it" works. Regardless of how good your spec is, once the coding is done the customer is going to realise that that's not what they actually wanted.

The problem is that the thing you use to build the transaction can also be used to directly manipulate the DB. A better API design would be to separate those two things.

The people using GenAI should be the ones doing the verification. The maintainer's job should not meaningfully change (other than the maintainer using AI to review on incoming code, of course).

Why does everyone who hears "AI code" automatically think "vibe-coded"?

The right to free speech only means you can't be prosecuted for what you say. It does not compel any private entity to distribute everything that you want to say.

Roughly, it used to be A330 vs 767 and A340 vs 777, the A330 and the 777 were the winners in these segments. The 787 was built to beat the A330, and it did, and the A350 was built to beat the 777, and it might.

Airbus reacted to the 787 with a re-engined A330, the A330neo, which was not a great success, but not a total flop. Boeing re-engined and enlarged the 777 to create the 777X, whose smaller variant positioned against the A350 is a slow seller, but whose larger variant, which has no direct competitor, has seen some sales - if Boeing manages to get it out of the door, the program is again hugely delayed and over budget.

A turbine-engined biplane for crop dusting.

NIO are already doing at least part of that by charging the batteries during time of excess energy only