by Serguey Shinder
There was a term that came up constantly on my first team. It was in the architecture diagrams, in stand-up, in the names of half a dozen classes, and I did not know what it meant. Not vaguely, not partially. I had no idea. I understood it the way you understand a word in a foreign language you have heard often, which is that I could tell when it was being used correctly without having any grasp of what it referred to.
I did not ask on day one because I assumed it would become clear. I did not ask in month two because by then I felt I should already know. And by the end of the first year, asking had become genuinely difficult, because the question was no longer just the question, it was also an admission that I had been nodding along in meetings for twelve months about something fundamental to the system I was being paid to work on. So I did not ask, and I got by, which was the worst possible outcome because getting by removed the pressure to ever resolve it.
Two years in, on a call with someone new who was asking basic things without apparent shame, I finally said it out loud. The explanation took about ninety seconds. It was not subtle, it was not hard, and about four separate confusions I had been carrying resolved themselves as he spoke, including one that had made me write a piece of code in a strange defensive way I could never have justified.
Ninety seconds against two years. I have gone back to that arithmetic many times, because the thing it exposes is not ignorance, it is the cost of protecting an image. I had been managing how I appeared at the direct expense of how much I understood, and the trade had felt reasonable at every individual moment while being catastrophic when summed.
What I noticed afterwards was that the people I most respected asked basic questions constantly, and it never once occurred to me to think less of them for it. The senior engineer who stops a design discussion to say he does not follow, and to ask someone to go back a step, is not exposing a weakness. He is doing the thing that makes the meeting useful, and everyone in the room silently benefits because at least two other people did not follow either.
So the rule I try to hold to now is that the discomfort of asking peaks early and then grows forever. Day one is free. Month six is awkward. Year two is a small crisis. Whenever I catch myself deciding to work something out later rather than admit I do not know it, I try to remember that later is always more expensive than this, and this is already the cheapest it will ever be.
– Serguey Asael Shinder
Leave a Reply