23 ms·
Here's my experience with these tools: Good: I can prototype things very quickly thanks to these tools Bad: After couple of vibe coding iterations, I don't ha
by willahmad 1y ago
Here's my experience with these tools:
Good: I can prototype things very quickly thanks to these tools
Bad: After couple of vibe coding iterations, I don't have a mental model of the project.
Good: When I open my past projects where I have very good mental models, I can come up with a nice prompt and build anything quickly again.
Bad: After couple of iterations I become lazy, and eventually my mental models break.
There's definitely a use for these tools. But be careful, job of engineers are not only coding but also training their memory to build solutions and bridge real world problem with software solution. If you lose this skill of thinking, you will be obsolete quickly
- accrual 1y agoThis matches my experience as well. When I'm working on a codebase that I started and know well, it feels like magic to chat with an AI and watch patches appear on the screen to accept/deny. I only accept about 50% of the AI patches before tweaks because it's my project and I care about keeping on the track I laid out. When I'm vibe coding something from scratch I don't have the mental model, I don't always review everything closely, and eventually it becomes an "AI project" that I'm just making requests against to hopefully achieve my goal.
- softwaredoug 1y agoAnd when you lose your mental model it’s harder to prompt the LLM for good code.