Keep a confusion log. One line, on any day something did not make sense.
Not a list of technologies you intend to study. Not a plan. Just the moment you were lost: the config that looked like it should have worked, the term two colleagues used as if it were obvious, the error you fixed without ever understanding why it went away.
That last one is the entire reason for doing this. Most confusion in a working day gets resolved by accident. Something starts working, the pressure lifts, and the question evaporates. You never decide to stop wondering. You just move on, and the gap sits there in your head exactly where it was.
The log catches those before they vanish.
Make it cheap or you will not keep it. One line, plain language, the way you would say it to a friend over lunch. I do not know what our load balancer really does with a request. I never understood why that migration needed a lock. Everyone says idempotent and I nod.
Then read it back once a week and look for repeats. The same thing appearing three weeks running is not a random gap. It is a foundation you are missing, and it is quietly making a dozen other things harder than they need to be. That is the one to go and learn properly. The rest can wait.
Two things happen that people do not expect.
You get much better at asking questions, because a written confusion is already half a question. Vague discomfort turns into something a colleague can answer in two minutes.
And you end up with a list of things to explain or write about later, once you do understand them. Whatever confused you is confusing somebody else right now, and you are the only person who still remembers what it felt like not to get it. That memory has a short shelf life. Six months from now you will find the topic obvious and have no idea what the hard part was.
Start tonight. One line about the thing that did not make sense today.
You already paid for the confusion. You may as well keep it.
– Asael Shinder
Top comments (0)