Chapter 2 - The Daily Friction of Modern Engineering

Most of my energy wasn't going into solving the real problem. It was going into recovering context.

Let me name the friction, because if you're a developer, you already feel it in your shoulders.

• Context switching. Docs in one tab, Stack Overflow in another, three Teams threads, two Jira tickets, a code review, and the actual editor I'm supposed to be coding in. Every jump costs me momentum.
• The blank screen problem. Starting from zero. Staring at an empty file knowing the shape of the thing but not the first line of it. That gap between intent and keystroke is exhausting.
• Boilerplate fatigue. Scaffolding I've written a hundred times. Config I'll never love. Tests that follow the same pattern as the last twenty. Repetitive setup stealing focus from real problem solving.
• An expanding knowledge surface. New languages, new frameworks, new SDKs, new platforms. The half-life of what I know keeps shrinking.
• The intent-to-code gap. I know what I want to build. The distance between knowing and shipping is where days disappear.

The truth I had to admit: productivity is flow efficiency, not raw output. I wasn't slow because I typed slowly. I was slow because I kept losing the thread. Every interruption forced a recovery cost, and modern engineering is all interruption.

This slide is the "before" picture. Hold onto it. Everything that follows is how I clawed those hours back, not by working harder, but by removing the friction that was eating me alive.