Skip to content

Optimization Mindset Spillover

Definition

People who spend their working hours finding and eliminating inefficiency in code tend to apply the exact same aesthetic — friction is bad, decisions should be automatable, everything measurable should be measured — to domains that were never meant to be optimization problems: relationships, appearance, where to live. What starts as a professional skill becomes an identity-level lens applied indiscriminately.

In the Book

Chapter 5 is built around Jason Ho, a San Francisco programmer who wrote custom route-optimization code to plan a Tokyo ramen-shop tour with his girlfriend Shelley, tracked his body-building diet in a spreadsheet down to "waxy maize" calorie counts, wrote software that scored candidate houses on projected long-term value before buying one, and built a personal "life guide" spreadsheet scoring sixteen life activities (from "entrepreneurship" and "coding" to "spending time with friends and family") on criteria like whether they "can be mastered" or are "autotelic." Thompson's diagnosis: "Programmers are obsessed with efficiency... nearly every one found deep, almost soulful pleasure in taking something inefficient and ratcheting it up a notch."

The chapter explicitly generalizes the trait beyond software by invoking Benjamin Franklin — "the original American hacker and engineer" — who invented bifocals purely to eliminate the friction of swapping two pairs of glasses, and a stove designed to save "Wood to the Inhabitants," framing today's coders as inheritors of an engineer's compulsion that predates computing itself.

Why It Matters

This names a specific failure mode of expertise: a tool that is genuinely valuable in one domain (systematic friction-removal in formal systems) gets over-applied to domains with different goods at stake — spontaneity, relationship, meaning — where measurement and automation can crowd out the thing actually being sought. It is a useful diagnostic for any profession built around a powerful method: ask which parts of the practitioner's life the method has quietly colonized, and whether that colonization is serving them or just running because the tool is there.