Simon Willison recently drew a line in the sand with his post on "[Vibe Engineering](https://simonwillison.net/2025/Oct/7/vibe-engineering/)." He distinguished between two fundamentally different ways of working with AI: the careless, prompt-and-pray approach of "vibe coding," and the disciplined, professional practice he calls "vibe engineering."

The Hacker News discussion that followed was predictably vibrant, debating everything from the term's seriousness to whether AI offers a 10% or 1000% productivity boost. One commenter aptly compared aimless prompting to the superstitious rituals of Skinner's pigeons, hoping for a random reward.

This conversation is critical because it forces us to move beyond the hype and define what it takes to use these tools professionally. Simon expertly identified *what* vibe engineering requires: robust testing, comprehensive documentation, good version control, and a "very weird form of management." But to truly move beyond vibe coding, we have to answer the billion-dollar question: *how* do you actually do it?

The answer is that the "vibe" is a misnomer. The feeling of a successful, intuitive collaboration with an AI agent isn't magic. It's the result of a rigorous, repeatable discipline. **To practice Vibe Engineering, you must master Context Engineering.**

### From Superstitious Pigeons to Scientific Process

Without a systematic approach, using AI agents feels exactly like the pigeon experiment. You tweak a prompt here, add a file there, and hope the agent's behavior changes for the better. This is the essence of vibe coding, and it's not engineering; it's superstition.

---
> This article includes Basic members-only sections.
> Upgrade to **Basic** to read the full version: https://slavakurilyak.com/membership