Vibe Coding

In vibe coding, you describe the feature you want, run what the model produces, and iterate on the behavior — accepting that you may not read or fully understand every line. For prototypes, throwaway tools, and exploring an idea, it’s a genuine step-change: working software in minutes instead of hours, with the human acting as director rather than typist.

The tension shows up when that code has to last. Skipping the read-every-line discipline trades away exactly what production needs — understanding, testing, security review, and maintainability — so the same loop that’s perfect for a demo can quietly accumulate risk in a real system. The recurring theme among builders on the show is that AI coding shifts effort rather than removing it: less time writing, far more time on specification, evaluation, and review.