Member-only story
My PM Started Vibe Coding Last Month. Now Every Feature Should Take an Hour.
It is the same conversation every sprint now. The demo looks finished. The timeline assumes it is. I am the one who has to explain why it is not.
She showed us the demo in sprint planning. She had built it over the weekend, she said. Pulled up her laptop, screenshared, walked us through it. A dashboard component with filters, a date range picker, a data table with pagination. It looked clean. The interactions worked. She said it had taken her about two hours using Claude.
Then she said: so I’m thinking we scope this as a one-day ticket for the engineering team.
I looked at the demo. Then I looked at my notes from the last three months of working with our actual data infrastructure. Then I looked at the demo again.
The component she had built connected to a hardcoded JSON file with forty-three rows of sample data. Our production database has eleven million records, partitioned across three services, with access controlled by a permissions layer that the demo did not know existed. The date range picker she had built did not account for our users’ time zone settings, which vary by geography in ways that had caused an incident eight months ago that…
