[nachocoll]

The "Deployment Hell" section is the most instructive part of this writeup. The AI could write the code but couldn't navigate the deployment environment — and you found that it was only by understanding the "why" behind the failures that you could actually get unstuck.

This is a pattern that shows up consistently in vibe coding experiences: AI excels at generating implementation within a well-understood context, but breaks down at system boundaries where implicit knowledge matters most. Deployment, authentication flows, third-party API quirks — these are places where the gap between "code that looks right" and "code that works in your specific environment" is largest.

What you discovered intuitively — that technical fundamentals are the "safety net" — is exactly what the Agile Vibe Coding Manifesto articulates: "humans remain accountable for software systems" and "generated systems remain understandable and maintainable." The beginner who learns why things fail, not just how to prompt around them, ends up with something genuinely theirs.

Great example of vibe coding used as a learning accelerator rather than a shortcut: https://agilevibecoding.org