12 points | by ahaucnx a day ago
3 comments
Just a guess, but I'm thinking this isn't going to get much traction because: 1) it just reads like an AI-written ad and 2) people have "vibe coding" fatigue.
Interesting, wishing you success.
What are your experiences with the debugging hell loop when the ai agent gets lost?
How do you avoid that or get baxk on track?
Different strategies.
- sometimes when it’s lost, just roll back. Commit very often. Sometimes it’s getting lost on simple and easy features - very unexpectedly.
- prompt regularly to review the architecture and clean up the code, check for specific things like code repetitions, error handling etc.
- keep an eye on the code yourself. At least on the general architectural side, and review complex code areas by hand
- ask always for larger features to make a plan first. Review the plan carefully. Only when the plan is ok, ask it to start coding.
Just a guess, but I'm thinking this isn't going to get much traction because: 1) it just reads like an AI-written ad and 2) people have "vibe coding" fatigue.
Interesting, wishing you success.
What are your experiences with the debugging hell loop when the ai agent gets lost?
How do you avoid that or get baxk on track?
Different strategies.
- sometimes when it’s lost, just roll back. Commit very often. Sometimes it’s getting lost on simple and easy features - very unexpectedly.
- prompt regularly to review the architecture and clean up the code, check for specific things like code repetitions, error handling etc.
- keep an eye on the code yourself. At least on the general architectural side, and review complex code areas by hand
- ask always for larger features to make a plan first. Review the plan carefully. Only when the plan is ok, ask it to start coding.