The index is built
Two junior engineers spent two days at a whiteboard reinventing the do-while loop in assembly. We knew what a do-while was. The gap wasn't the concept, it was the index: the connection between knowing something exists and reaching for it in the moment.
My first real engineering job, master's degree, zero production scars. A teammate and I were handed a problem (a loop that runs at least once before checking a condition), left completely alone, and we built something correct in assembly over two days and several whiteboard markers. We presented it to our tech lead, who said: "You mean a do-while?" We knew what a do-while was. That wasn't the problem.
Key takeaways
- Knowing a concept isn't the same as reaching for it in the field, and almost nobody names that gap directly
- Senior engineers don't think harder, they pattern-match faster: someone built the index for them, or they built it over years of edge cases
- What helps most in mentorship isn't harder problems, it's people who give you the words: an hour with someone who can name the thing beats two days at a whiteboard
- If you're the tech lead: go check on the whiteboard, just to hand over the missing index entry; the isolation was the failure, not the discovery
Who this is for
Junior engineers asking "how do I get faster" or "how do I think more like a senior," and the people mentoring them. Short personal essay.
The full story is on Substack.