A pilot, mid-flight, reading How to Become a Pilot. The plane is in the air. The pilot is at the controls. The book is open. These three facts should be mutually exclusive. In software engineering, they are simultaneously true at all times.
The absurdity is the job
A surgeon does not open a textbook during an operation. A lawyer does not flip through tort law during cross-examination. In every other profession, learning while doing signals catastrophe.
In software, it's Tuesday.
Three months into a React job, the senior engineer quits. You are now the frontend lead. You have never led a frontend. The React docs are on your second monitor, pull requests on your first. The plane is at cruising altitude. You are becoming the pilot by piloting.
Nobody hires a software engineer expecting them to know the stack. They expect them to learn the stack faster than the stack can break. The job is not knowing. The job is learning at altitude.
Why this works
Software is uniquely learnable in production. The feedback loops are tight. The cost of a mistake is a broken build, not a broken fuselage. And the knowledge required to fly any particular software plane is so contingent — on decisions made by people who left three years ago, on a legacy monolith whose variables are named after Lord of the Rings characters — that no amount of pre-flight training could cover it.
The plane you're flying was assembled mid-air by seventeen previous pilots, each with their own book open. The manual was written by the third pilot, updated by the seventh, contradicted by the twelfth. It's wrong in three places. You'll discover which three by flying.
When it gets dark
In a healthy career, the book eventually closes. Emergency learning — Stack Overflow in one tab, SSH in another — should be a phase.
When it becomes permanent, it stops being a metaphor for learning. It's burnout. The pilot reading for fifteen years straight is not brave. They're a staff engineer who never gained confidence, in a profession where the plane keeps getting more complex and the manual keeps getting thicker. The passengers keep asking when they'll arrive.
The difference between a junior and a senior: the senior knows which pages of the manual to ignore.
Learning to fly is flying
The pilot reading the book is, against all probability, still flying. The plane hasn't crashed. This is not luck. This is a skill.
The skill is not reading manuals. It's not operating aircraft. It's doing both simultaneously, under time pressure, without panicking — encountering a problem you've never seen, in a system you partly understand, with a tool you're learning as you use it, and producing a working outcome before the fuel runs out.
The destination is 3,000 miles away. The fuel is good for 2,800. You figure out the rest in the air. That's the job. The book will help. The book will also be wrong. You'll know which parts when you need them.
Every engineer who ever shipped anything learned to fly while flying. The ones who waited to feel ready never left the ground.