Comment by funnyfoobar

To be honest, what you have described only shows lack of process.

I am not talking about vibe coding here, which is totally different and understandable. But I am talking about the professional context where the structure is already in place.

Here is my workflow, if it helps:

1. I have a system level prompt i execute(command/skill) before I start anything which says things like

    i) follow SOLID principles
    ii) follow TDD
    iii) follow these testing principles like, don't test the implementation details etc
    and 20 other things

2. I give it the context of what I need to accomplish, and toggle the plan mode ask it follow the above things I have set at system level, and generate me a document to review step by step

3. I review everything, add feedback to the generated plan, prompt again, and finally finalize the plan

4. now that the plan is finalized, I would have a small alignment with co-workers and ask it implement step by step, and then before proceeding with next step, i will tell it to ask me for feedback

each steps code is reviewed and commited, before proceeding to next step

5. once all steps are done, manual testing is done, i do a local review

6. I have a specific skill which reviews everything, and gives me feedback

7. we have human reviewers who will review the code, and coderabbit

8. then we take it to the staging and uat before taking to prod

so see we have not skipped any process of "software engineering", claude code is just an accelrant

but if you are not doing most of the above steps, i see what you are saying would happen by default