There's been a vibe shift in vibe coding


Le Taureau (The Bull) by Pablo Picasso — a series of eleven lithographs showing the progressive abstraction of a bull
Pablo Picasso, Le Taureau (The Bull), 1945–1946 [Reversed]

Just after Christmas something changed in the attitudes of the senior engineers I follow. LLM coding took another step forward.

Skeptics became converts, and converts became bulls.

We might be around 6 months from Jonathan Blow getting onboard.

In the past this has seemed like bluster and people hyping things up for attention. I’m thinking of 9 months ago when Tobi Lutke posted “Reflexive AI usage is now baseline expectation at Shopify”.

But now? I dunno if it’s because I got ChatGPT Pro recently or because Opus 4.5 dropped and became my daily driver in Cursor, but the capabilities of coding agents feel much better.

Here’s what changed: the defining feature of vibe coding—shipping code without reading it—is becoming an accepted practice by highly skilled, staff+ engineers. What has replaced vibes is specification, where the engineer uses their skill to define the solution and then trusts the coding ability of the agent to autonomously implement and test itself against the solution spec. Spec-driven development.123

This gain of trust has dilated pupils and spiked ambition.

Heady days.