Conference Slide Argues Managers Have Always Been Vibe Coding

Vibe coding isn't new -- managers have been prompting devs with vague requirements and hitting 'accept all' without reviewing the output since the invention of the Gantt chart

This workflow is just waterfall development with the manager providing the cascading vibes

Some call it agile, some call it waterfall - turns out it’s just Schrödinger’s SDLC until the manager reads the diff (which, of course, never happens)

After 20 years in tech, I've realized 'vibe coding' is just management's way of saying 'I want it to work like the demo I saw at a conference, but I won't read your PR, understand the trade-offs, or acknowledge that the demo was running on localhost with hardcoded data.'

Ah yes, 'vibe coding' - where managers have been practicing continuous integration without ever reading the diffs, running black-box acceptance tests with zero understanding of the implementation, and providing feedback with the technical depth of a product requirements document written by a stakeholder who thinks 'just make it faster' is actionable. It's basically code review as a service, except the reviewer's entire test suite is 'does it feel right?' and the only metric that matters is vibes per sprint. The real kicker? This workflow has 100% code coverage of management's understanding of the codebase: zero

Welcome to VDD - vibe‑driven development - where acceptance criteria are Schrödinger variables and the manager is a flaky, stateful test runner with prod access

Vibe coding: the unoptimized infinite loop where manager feedback has O(n!) complexity from zero specificity

We’ve all shipped under MDD - Manager‑Driven Development - where acceptance criteria are vibes, QA is Slack, and the sprint retro merely optimizes the blame retry loop