I'm 26, and even now there can be a particular kind of frustration that comes with learning something new.
Studying software engineering gives me plenty of reasons to think about that. There’s always another concept to understand, another problem to work through, another detail I’ve overlooked. It’s easy to measure a study session by how much material I finished. However, understanding is harder to measure.
Sometimes the most valuable work occurs on the very problem that keeps me from moving on.
Giving a Problem Enough Attention
Code gives you immediate feedback. It runs, produces an unexpected result, or throws an error. That feedback is useful, but getting a program to run is only part of learning how it works.
I want to be able to explain why a solution works, what assumptions it makes, and what would happen if the input changed. Those questions ask more of me than following an example. They require me to slow down, trace the steps, and notice where my explanation becomes uncertain.
An algorithm can look simple on a slide. Working through it by hand reveals the decisions hidden inside that simplicity. Each comparison, each repeated step, each change to a value has a purpose.
Taking the time to understand those details gives me something I can use again. The next problem may look different, but I have a better place to start.
Reading, but with Room to Pause
Reading offers a quieter version of the same experience.
A page can be easy to finish and difficult to absorb. I can recognize every word in a paragraph and still need time to consider what the author is saying. A passage might deserve a second reading, a note in the margin, or a few minutes with the book closed.
I like having a collection of books I can return to. It leaves room for a different kind of relationship with reading: remembering an idea, reconsidering it, and finding something useful that I missed before.
There’s satisfaction in finishing a book, sure, but there’s also satisfaction in carrying one good thought away from it and continuing to work through that thought afterward.
A Beginner, Again
I once worked with an older man who told me that what he disliked most about being young was how much he didn’t understand. I can see what he meant. Experience gives you perspective that’s difficult to have when you’re just starting out. Still, I see it a little differently. At any age or stage of life, there’s more to learn and an opportunity to apply yourself. Taking initiative as an initiate- that's a yearning I never want to lose.
That takes a willingness to admit when an explanation didn’t stick, ask a "dumb" question, or revisiting a familiar concept. Sometimes it means spending another evening on something you expected to understand already.
Those moments can feel discouraging, especially when everyone else’s progress seems so visible. Finished projects and polished work are easy to share. The hours spent confused usually stay out of sight.
I’m trying to give those hours a fairer place in how I think about learning. Recognizing what I don’t understand helps me figure out where to put my effort. Being able to explain something more clearly than I could yesterday gives me a reason to keep going.
