THE EDGE OF VIBE CODING

A few months back, I wrote about the promise of vibe coding. Now, 2.5 months into practicing it daily, I still believe the nature of programming has shifted. But I'm also seeing the current limits more clearly.

The biggest friction point comes when a project needs to interact with external data. Whether it's a database or API calls, progress slows down significantly. This happens regardless of the model being used.

Right now, the best move is to delay database integration. In the early stages, the data model needs to stay flexible. File-based formats like JSON work better and are easier for the LLM to navigate. Once you involve a real database, errors become more frequent and the process becomes much harder to manage.

Keep it local as long as possible. That's where vibe coding still flows.