Post #606132

Letting Claude Code work creates a kind of an escalator effect. You feel you're moving so you stop walking. Instead, you should actually be thinking how to keep feeding signal to it, improve the quality of requirements, so that it can keep working and not just continue rolling towards the average archetypal software project of your domain. Because that is what it will do if you just let it roll. You're like a project manager, removing obstacles to work, building channels of high quality information and feedback to guide the project to a good direction. I personally feel like Claude Code is already too efficient in transforming requirements to code. It doesn't leave the user enough time to think what is actually wanted. A single person is not enough to feed it high quality material fast enough, as fast as it runs through it. So, the bottleneck is now in the high quality requirements definition, and this is the most common place where an automated software project fails. At least with traditional software projects there was more time to think about the requirements and engage all the stakeholders. Now this gets compressed and the results are often as one would expect. #AI