Vibe coding and technical debt
Don’t get me unsuitable: I recognize the unbridled creativity that may be present in simply using a vibe on an AI platform. In case you haven’t already tried it, I recommend sitting down with Roo Code and seeing the way it feels to blast out working software program with only a few keystrokes.
At first, vibe coding is intoxicating. You may quickly produce all the fundamental utility infrastructure with out even interested by it. It’s like driving a 4×4 that sails over velocity bumps. Fairly quickly, although, you can find your self off-roading within the ravines of wack-a-mole fix-and-break, just like the above person did. All of the sudden, that panorama of magically practical code turns into a yawning chasm of technical debt that you need to determine. And in case you don’t have the coding background to know what you’re up towards, you’ll drown in it.
Positive, you possibly can attempt utilizing AI to repair the issues which might be breaking, however have you ever tried it? Have you ever ever been caught with an AI assistant confidently operating you and your code round in circles? Even with one thing like Gemini CLI and DevTools integration (the place the AI has entry to the server and client-side outputs) it might probably so simply descend right into a maddening cycle. Ultimately, you’re mocked by your individual unwillingness to roll up your sleeves and do some work.
