Reading Is the New Coding

The problem

PRs are up. Specs are up. Your eyeballs did not get a 10x.

PRs are up. Specs are up. Every meeting spawns a transcript, a summary, and a Slack thread arguing about the summary. You still read at ~250 words per minute. You still need 7 hours of sleep. The math is not on your side.

Production scaled exponentially. Your attention scaled by zero. The dashboards say green. You are drowning in green.

The trap

You’re trying to read it all. Adorable.

The “good engineer reads everything” instinct was already wobbly in 2019. In 2026 it’s a math error. A 40-person team running agents ships maybe 200 PRs a week. At 5 minutes each that’s a 16-hour reading job. You have not written code. You have not slept. You have read PRs.

Open any engineering Slack right now. The 👀 reacts on PRs outnumber the ✅ ten to one. People aren’t reviewing. They’re performing reviewing.

The ones thriving are reading less, choosing harder, and somehow look better-rested than you. Their over-informed colleagues are busier, twitchier, and shipping less. Reading everything used to mean you cared. Now it means you haven’t picked.

The shift

Producing got cheap. Reading is where the leverage is hiding.

Senior engineering used to be ~30% reading, ~70% producing. Flip it. Producing got cheap. Reading is where the leverage is hiding.

Triage is the new skill. It looks like:

• Skim, read, skip — and knowing which inside 10 seconds.
• Saying “I’m not reviewing that” without the apology voice.
• Trusting summaries 90% of the time and knowing the 10% when you can’t.

You will feel less informed. You will be less informed. The only question that matters: less informed about the right things, or the wrong ones?

The toolkit

Six moves, all measurable

1. Default to no-read. Opt in, not out. If it doesn’t @ you, name you, or block you, skip it. The things that actually need you will find you twice.

2. Tier your sources. Tier 1 (read fully): cap at 5. Tier 2 (skim weekly): cap at 15. Tier 3 (search on demand): everything else. If your Tier 1 has 40 things, it’s a list.

3. Make the agent read first. 30-page RFC → 1-page summary + 3 real questions. Target 10x compression before you spend a single neuron. Summaries are cheap. Your judgment isn’t.

4. Cap your reviews. Pick a number and post it somewhere visible. Suggested floor: 3 serious PR reviews, 2 design docs, 1 postmortem per week. Past the cap you decline with a reason. Capacity you don’t declare gets eaten by people who needed you to say yes.

5. Write less, link more. Every doc you write is a doc someone else has to read. Before writing: search. If it exists, link. If you must write, target half the length you had in mind. Half again if it’s a status update.

6. Defend 90 minutes a week of deep reading. One thing. Not seven things. On the calendar. Labeled. Decline conflicts. This used to happen by default when production was slow. Production is no longer slow.

One last thing

The new senior skill is not reading things

The engineers who can say “haven’t read it, not going to” — and then absolutely cook on the things they did read — are operating on the right model.

Three buckets, from today:

• Know deeply: ~5 things.
• Know via summary: ~50 things.
• Will never know: everything else. By volume, this is most of what is happening at your company. That’s not a failure of diligence. It’s the math, and the math is not going to apologize.

Read less. Read better. Pick.