The index is built
(and nobody told you that was the job)
My first real engineering job was at a defense contractor. At the time I had a master’s degree, working knowledge of data structures, and exactly zero production scars.
My teammate and I were handed a problem. A loop that had to execute at least once before checking a condition. Nobody checked in on us. We went to a whiteboard and were left completely alone. We went through multiple markers. The cap on one of them went missing and we stopped caring around noon.
And then we built… something… in assembly. Traced through the logic four times. It was correct. We walked to our tech lead’s desk and presented what we’d built.
“You mean a do-while?”
Here is the thing I want to be clear about: we knew what a do-while was. It was in the textbook. If you had said the words on the street, I would have defined it correctly. That was not the problem.
The problem wasn’t the logic. It was the index. The connection between “I know this kind of loop exists” and actually reaching for it in the moment.
Knowing a concept in isolation is not the same as being able to reach for it in the field. That gap is real and almost nobody talks about it directly. We treat experience like it’s about intelligence, or exposure to hard problems, or just time served. It’s not. It’s about having a pattern library with a working index.
Senior engineers don’t think harder. They just pattern-match faster. Either someone built the index for them, or they built it themselves over time, through enough weird edge cases that things start to click.
Two junior engineers alone in a room will arrive at the right answer. They will just do it in four times more code than necessary, give it no name, and have no idea the door had a handle.
This comes up in mentorship conversations constantly, usually as “how do I get faster” or “how do I think more like a senior.” And honestly, the thing that helps most is just finding people who will give you the words. Before you spend two days at a whiteboard, spend an hour with someone who can name the thing you’re looking at. The construct probably already exists. The name is probably going to make you feel slightly foolish and massively relieved.
And if you’re the tech lead: go check on the whiteboard. Not to supervise. Just to hand someone the index entry they’re missing.
The discovery wasn’t the failure. The isolation was.
This is part of a longer story from [Chaotic Commits]