The Two Modes of Thinking, Personified
Writer Tim Urban crystallized the distinction between analogy and first principles using a memorable metaphor: the Cook and the Chef.
-
The Cook (Reasoning by Analogy): The Cook relies on recipes. They look at what others are doing (Netflix, Google, "Best Practices") and replicate it. If the recipe says "Add 2 cups of sugar," they add 2 cups, even if they don't know why. This is efficient for day-to-day execution but fails when you need to innovate, when the context changes (e.g., you're cooking at high altitude where boiling points differ), or when you run out of an ingredient and don't know what to substitute.
-
The Chef (First Principles): The Chef understands the chemistry of flavor. They know that sugar serves specific functions: sweetness, browning via the Maillard reaction, moisture retention, and structural support in baking. They don't need a recipe; they can create a new one from scratch because they understand the fundamental truths of the ingredients. When they run out of sugar, they can reason about whether honey, maple syrup, or simply reducing the quantity would achieve the same functional goal.
The Engineering Trap
Most engineers operate as Cooks. We use React because "Facebook uses it." We adopt microservices because "monoliths are old." We add Kafka because "event-driven architecture is the future." This is analogy. It works until you reach the edge of the map—where your scale, budget, team size, or constraints differ from the company you are copying.
The trap is subtle because analogical decisions often feel rigorous. You read blog posts, watched conference talks, and compared alternatives. But if every alternative you considered was itself an analogy ("should we use Kafka or RabbitMQ?" instead of "do we need a message broker at all?"), you never left the recipe book.
How to Tell Which Mode You're In
Ask yourself this diagnostic question about any technical decision: "Can I explain why this is the right choice without referencing any other company or 'best practice'?"
- "We use Postgres because our data is relational, our query patterns require complex joins, our team has deep Postgres expertise, and our dataset fits comfortably on a single node." → Chef.
- "We use Postgres because it's the industry standard for relational data." → Cook.
Both might choose Postgres. The difference is that the Chef knows exactly when Postgres would be the wrong choice and can articulate those conditions.
When asked "Why did you choose X technology?" in an interview, interviewers are testing whether you're a Cook or a Chef. Never answer with "because Company Y uses it" or "it's the industry standard." Instead, articulate the specific constraints (latency requirements, team expertise, budget, data access patterns) that led to your decision. Then mention one scenario where you would have chosen differently. This demonstrates engineering judgment, not just tool familiarity.
Key Point: The Cook/Chef distinction is not about intelligence—it's about awareness. Many brilliant engineers operate as Cooks because they've never been taught to question the recipe. The first step to becoming a Chef is simply noticing when you're following a recipe and asking: "Do I understand why this recipe exists?"