> The power of AI is not the 'nits and small bugs' - it's the firehose of scratch branches it can let loose in where it doesn't have to worry about PRs, reviews.
> Once it's all figured out, then the path to the solution is actually relatively clear - and it can be 'planned out' and just done.
it is important to be clear about what this buys: quick coding and testing primarily.
the mental effort needed to design, manage the constraints and all other essential workflows to bring about a professional product is still present.
I don't agree on 1, partly yes on 2.
What it buys is a clear path through the mess without having to make it.
I'm saying: 'figure out the design and constraints by discovering them ... instead of trying to 'one-shot' them as a human'.
By the time you've run the gambit 100 times - you can synthesize the learning into something that's nearly complete.
Let the AI figure out the constraints, you just guide that. It can't do it in conversation, it takes a lot of iterative prodding.
But yes you have to decide where to steer it, and this only works for certain kinds of engineering at a certain scale.