What exactly is Vibe Coding?
Vibe Coding means that you, as the architect and decision-maker, set the intent and direction of the product while AI does a large share of the implementation at speed. It is not the end of engineering — quite the opposite. Architectural decisions, precise problem framing and reviewing the output matter more than ever.
Why now?
In a few years language models went from autocompleting a few lines to agents that can write a whole module, run its tests and fix their own mistakes. The bottleneck of development is no longer typing code; it is clarity of thought.
What it looked like in practice
- CeritaMed: the enterprise management system and the "Dental Companion" SaaS — dental charting, treatment plans, accounting, SMS reminders — were delivered in a time frame that would traditionally have needed a multi-person team.
- Hunter: a full digital adaptation of a board game with Flutter and Flame, plus a NestJS licensing server.
- Projehban: an app that ships its own MCP server so AI agents can plan inside it directly.
The rules I keep
- I own the architecture. Module boundaries, the data model and API contracts are human decisions.
- I run everything. Code that has not been executed and tested does not exist.
- Security is non-negotiable. Parameterized queries, input validation and proper session handling are never left to chance.
- Small steps, fast feedback. Every change is small, reviewable and reversible.
The takeaway
For someone who deeply understands the problem, Vibe Coding is a multiplier. The future belongs to builders who know what should be built and use AI to build it fast and right.