You Are the Compiler Operator
A compiler doesn't write programs. It translates them. You give it source code with clear syntax, type constraints, and defined semantics, and it produces something runnable. Give it ambiguous input and you get errors. Give it nothing and you get nothing.
AI works the same way. Instead of code, you're feeding it intent. The quality of what comes out is a direct function of how clearly you specified what went in. You are the programmer. The model is the compiler. Your job is to write specs it can work with.
The most important specs aren't the ones you write in a prompt. They're the ones you establish before you open a chat window.
Stack, libraries, database, deployment setup, design system, architectural invariants (the rules your system must never break, like "this service is always read-only" or "all writes go through this queue"). One developer I follow called these "the laws of physics" for a project. They define the space the model is allowed to work in. Leave them undefined and you'll get technically plausible output that doesn't fit your system. Changing those decisions later is expensive.
The instinct to start generating immediately is understandable. It feels productive. But a model working without constraints isn't faster, it's undirected. You'll spend more time steering it back than you saved by starting early.
The compiler analogy also explains where things go wrong. A compiler can only work with what it's given. It doesn't know what you meant. It doesn't know what came before or what will come after. It produces output that satisfies the spec you wrote, not the intent you had.
AI has the same ceiling. If the context is shallow (a one-line prompt, no codebase conventions, no description of constraints) the output fills in the gaps with plausible-sounding defaults. Those defaults may be reasonable in isolation and wrong for your situation.
One line I keep coming back to: "Claude might give you a Ferrari, but it doesn't stop it from driving into a wall if you let go of the wheel." The operator is always responsible for the outcome. That's not a limitation to work around. That's the nature of the tool.
Defining constraints upfront isn't overhead. It's the work. The engineers getting the most out of AI invest in context: clear convention files, well-documented architecture, explicit invariants, tests that encode intended behavior. They're not writing more prompts. They're building a better compiler target.
Part 5 of 14 — What I Think About AI Engineering**
← Faster Output Demands a Higher Quality Bar AI-Native XP: A New Workflow Emerges →