The skill no tutorial teaches — but every senior dev has
Nobody writes the code you'll spend most of your career reading. It lands in your lap as a pull request, an inherited repo, a library you're debugging at 2 a.m. The ability to navigate it quickly — to build a mental model of a codebase you didn't author — is the actual job, and it's almost never taught.
Most learning content is shaped around writing: here's a concept, now implement it. Reading is the mirror skill, and it compounds differently. A developer who reads widely and deliberately picks up idioms, patterns, and failure modes that would take years to rediscover solo. That's the gap between someone with three years of experience and someone who feels like eight.
How to actually do it
Start with the entry point, not the most interesting file. For a Node server, that's usually index.ts or wherever the process bootstraps. For a front-end app, it's the router or the root component. Resist the pull of clever utility functions until you understand what the system is trying to do. Orientation before detail.
Then follow the data. Pick one real user action — a form submission, an API call, a button click — and trace it through the stack. You're not trying to memorize; you're building a map. Where does the data come from? What transforms it? Where does it land? This single exercise tells you more about a codebase's real architecture than any README.
Read tests second, not documentation. Tests show what the author believed the code should do, under conditions they thought were worth specifying. A well-named test suite is a cheat sheet for intent. When documentation lies (and it will), tests are often still honest.
Notice what isn't there. Missing error handling, no retry logic, a suspiciously empty catch block — these absences are as informative as the code itself. A codebase's blind spots are your map of its risk surface.
The deliberate practice angle
Open-source is a free library of the world's production code. Pick a tool you already use — a small utility, a Vite plugin, a well-regarded React hook library — and read it properly. Not to learn the tool's API, but to study the decisions: how errors are surfaced, how the public interface is separated from implementation, where the author reached for simplicity over cleverness.
Do this regularly and something shifts. You stop feeling lost in unfamiliar code. You start recognizing patterns across projects. You get faster at the parts of the job that can't be outsourced to autocomplete. Shipping your first real project gets you in the door; reading other people's code is what keeps you growing once you're through it.