| ▲ | troupo an hour ago | |
No. The issue is: "I notice too many things (redundant code, duplicate code, overly complex architecture, etc.) during review" How does "low-stakes environment" fix that? | ||
| ▲ | stillpointlab an hour ago | parent | next [-] | |
Because one may learn that those fears are overblown. Or they may learn that they cannot build any kind of software without reviewing every line of code. The person is saying "I am still unable to stop" and that is most likely because they feel a sense of responsibility. If they choose a project where there is no responsibility, where it literally doesn't matter if the project fails, they may feel able to stop. And if they manage to make that project work, if they can succeed, then they will build up confidence. It seems better to be able to work both on projects where they review all code as well as projects where they do not review any code. In fact, keeping their job in the long term may (or may not) require having both skills. | ||
| ▲ | jazzyjackson an hour ago | parent | prev [-] | |
I guess they’re just saying “you’re holding it wrong” Last time I chose to vibe code, I did it in a language I didn’t know so that I wasn’t tempted to try and comprehend the choices the robot made. I ended up with the application I wanted. Caveat: it was code I would never have to touch again, I ran a script to generate the 140,000 static html pages that the rails app provided and then just uploaded them all to R2 buckets (million reads per month on free tier) | ||