One month after "vibe coding" entered the chat, the novelty is thinner and the tickets are thicker. People are shipping weekend apps with coding agents, then drowning in bugs they cannot read.
What got faster
UI scaffolds, CRUD flows, glue between APIs. Demo day arrives before lunch. That is real leverage for MVP experiments.
What got riskier
Security defaults. Auth mistakes. Dependency soup. Debug sessions where the author cannot explain a function the model invented at 1 a.m.
Vibe coding is fine as a power tool with review. It is reckless as a substitute for literacy. March is the practical follow-up: speed is easy, ownership is the scarce skill.
A useful rule of thumb: if you cannot sketch the architecture on a napkin, you are not done, you are rented. Agents can type faster than you. They cannot care about your pager.
Keep the vibes for spikes. Keep literacy for anything with users or money.
The details will keep shifting. The underlying tradeoff in this moment stays clear enough to write down while it is fresh.
Brak komentarzy:
Prześlij komentarz