How I approach vibe coding projects to make it not suck

1 pointsbwooceli25d ago1 comments

Since everyone's tired of GPT submissions, I super-swear this is just me and a keyboard.

1) Write the backend in python using test-driven development. The bot can run the test suite and self-correct as it goes, and greatly reduce the blast radius when it tries to do something "stupid"

2) Write the front end with typescript. Same reason. Super fragile, typescript checks as it goes to make sure things are mostly done right.

that's it, have a nice day.

1 comments

nachocoll16d ago

This is genuinely good advice, and the TDD approach is underrated in vibe coding contexts. Tests give the AI agent a deterministic verification loop — it can self-correct against actual specifications rather than guessing from prompts. TypeScript's type system doing the same for the frontend is the same instinct.

Both approaches map to a principle from the Agile Vibe Coding Manifesto (https://agilevibecoding.org): "Systems remain deterministic and verifiable — software behaves predictably and is verified through tests." The manifesto extends Agile principles to AI-assisted environments, and this pair — typed frontend + TDD backend — is about as robust a foundation for vibe coding as you can get.

The other piece worth adding: the fact that you're writing the tests (expressing intent) and letting the bot implement to green is exactly right. Traceable intent is what separates maintainable vibe-coded projects from ones that collapse after a few iterations.

j / k navigate · click thread line to collapse