You Are Learning. But Are You Enjoying It?

How the abundance of knowledge quietly changed the way we learn.

There is a question that rarely gets asked in software development, buried beneath tutorials, roadmaps, certifications, and course recommendations:

Are you actually enjoying what you're learning?

Not Are you keeping up? Not Are you learning the latest framework? Not Have you completed another course?

Simply this: Are you enjoying the process of learning?

It is a surprisingly difficult question to answer honestly.

I began programming in 1995. At that time, learning software development looked very different from what it does today. There was no YouTube to explain concepts in fifteen minutes. There were no online courses with downloadable source code. There were no blogs publishing tutorials every day, and there certainly wasn't an AI assistant waiting to answer every question instantly.

Our teachers were books, compiler manuals, product documentation, and the built-in Help menu that came with development tools. If you got stuck, you experimented. If that failed, you searched through another chapter. Sometimes the answer was hidden in a single paragraph of a six-hundred-page book.

Learning was undeniably difficult.

Yet, strangely, it was also immensely enjoyable. I still remember buying programming books that were well beyond my level, simply because the topics fascinated me. I would read them chapter by chapter, writing small programs just to see what happened. Much of it didn't make sense the first time, but every experiment taught me something. Looking back, I probably learned more from those evenings of curiosity and experimentation than I realised at the time.

When Scarcity Forced Depth

What that era lacked in resources, it made up for in attention.

When a book was your primary source of knowledge, you didn't skim it looking for the answer. You read it carefully. You built mental models. You sat with confusion until it resolved. If something didn't work, you kept trying until it finally made sense.

Every solved problem felt earned.

Hours disappeared while tracking down a misplaced semicolon. Entire weekends were spent understanding pointers, memory management, or object-oriented design. Today, a five-minute video or a single AI prompt could explain the same concept.

But difficulty and enjoyment are not opposites.

In fact, some of the deepest enjoyment comes only after genuine difficulty. The satisfaction of finally understanding something after struggling with it is unlike anything that instant answers can provide. The struggle wasn't slowing the learning down. The struggle was the learning.

Learning as Conversation

Then came the Internet, and with it, an extraordinary transformation.

Online forums, mailing lists, Usenet groups, CodeProject, Stack Overflow, and countless developer communities connected programmers across the world. Learning was no longer a solitary activity. It became a conversation.

Good communities didn't simply provide answers — they taught us how to ask better questions. You learned to explain your problem clearly, describe what you had already tried, and think carefully before posting. Reading discussions exposed you to different approaches, trade-offs, and ways of thinking that extended far beyond the original question.

The community became the curriculum.

Stack Overflow in its early years was a remarkable epistemic institution. The incentive to answer correctly, not just quickly, was built into the system. Developers who grew up in that environment learned not just solutions, but a discipline of thought — precision in problem formulation, rigour in verification, honesty about uncertainty.

The Internet didn't diminish the joy of learning. It amplified it.

The Paradox of Abundance

Fast forward to today.

Books, ebooks, video courses, interactive platforms, YouTube channels, podcasts, blogs, GitHub repositories, online documentation, and AI assistants have made knowledge available almost instantly. From a technological perspective, this is extraordinary. We have more learning resources than any generation of developers before us.

Ironically, many of us enjoy learning less.

Abundance creates challenges that scarcity never did. There are hundreds of courses for every technology. Thousands of videos promise to teach the same concept. Every week introduces another framework, another language, another AI tool that everyone insists you should learn immediately.

Instead of asking "What am I curious about today?" we find ourselves asking "What should I learn next?"

Curiosity quietly gives way to obligation. Somewhere along the way, learning stopped feeling like a hobby and started feeling like career maintenance. What once felt like exploration now feels like staying afloat.

When Learning Becomes Performance

Modern developer culture has also changed how learning is perceived.

Learning is no longer just something we do. It is something we display.

Social media has amplified this shift. Certificates are announced. Course completions are shared. Learning streaks are celebrated. Sharing progress isn't the problem — the problem begins when demonstrating that we're learning becomes more important than actually understanding what we're learning.

Instead of studying something because it fascinates us, we study it because we want to appear continuously current. Understanding becomes secondary to visibility. The joy quietly disappears, replaced by the performance of learning.

The Hidden Cost of Endless Resources

The greatest challenge today isn't the lack of information. It is the constant, undiscriminating consumption of it.

We watch videos at double speed. We bookmark articles we'll never read. We buy books faster than we finish them. We enrol in more courses than we could possibly complete. Sometimes we mistake consuming educational content for actually learning.

There is another cost: decision fatigue. With hundreds of resources available for every topic, we spend an astonishing amount of mental energy deciding how to learn instead of simply learning. We compare courses, watch reviews, ask for recommendations, and build elaborate learning roadmaps before writing a single line of code. The meta-work begins to consume the real work.

Curiosity or Fear?

Perhaps the biggest change over the past three decades isn't technological at all. It's psychological.

When I started programming, I learned because I was fascinated. Today, many developers learn because they are afraid — afraid of becoming obsolete, afraid of missing the next big trend, afraid that everyone else is moving faster.

Learning becomes reactive instead of joyful.

Curiosity says: I want to understand this.

Anxiety says: I have to learn this before I'm left behind.

Those motivations may produce similar short-term outputs, but they create entirely different experiences. Curiosity energises. Anxiety exhausts. And crucially, only one of them sustains a decades-long career.

AI: Colleague, Not Oracle

Artificial Intelligence has become the newest chapter in the story of learning, and its capabilities are remarkable. It explains concepts, reviews code, generates examples, summarises documentation, and saves hours of frustration. Used thoughtfully, it is one of the most powerful learning companions we have ever had.

But it introduces a subtle temptation: every obstacle can appear to vanish with a single prompt.

Sometimes that is exactly what we need. Sometimes it isn't. Many of the lessons that shaped us as developers came from moments of confusion — when we misunderstood a concept, built something incorrectly, debugged for hours, and finally experienced that unmistakable moment when everything clicked. If every struggle disappears instantly, some of those formative moments disappear with it.

The goal is not to avoid AI. The goal is to treat it as a thinking partner rather than an answer dispenser. Use it to challenge your reasoning. Ask it to explain why something works, not just how. Don't outsource your curiosity.

Making Learning Enjoyable Again

The solution is not nostalgia. Today's learning tools are extraordinary, and the right response is not to abandon them — it is to be more deliberate about how we use them.

Choose depth over coverage. One deeply understood concept is worth far more than ten half-finished courses. Read the source code. Understand the reasoning, not just the syntax.

Deliberately create constraints. Instead of collecting five books and ten video courses on the same topic, begin with one good resource and stay with it. Constraints force engagement.

Build more than you consume. Watching tutorials can inspire you, but writing code — and breaking it, and fixing it — is where understanding takes root.

Sit with the problem a little longer. Resist the urge to search immediately. The struggle often contains the lesson.

Follow curiosity, not anxiety. The next time you decide what to learn, ask honestly: am I curious about this, or am I afraid of falling behind without it? The answer should shape the decision.

The Bottleneck Has Changed

Thirty years ago, the challenge was finding knowledge. Today, the challenge is protecting our attention.

We have moved from an age of information scarcity to an age of attention scarcity. The bottleneck has changed — and that changes everything.

The developer who patiently explores one idea often learns more than the one who races through ten courses. Depth still matters. Curiosity still matters. Enjoyment still matters.

Because the developers who continue learning for decades are rarely the ones chasing every trend. They are the ones who never lost the excitement of discovering something new.

A Final Thought

I don't miss slow computers or searching through thick manuals for a single API reference. Today's learning tools are nothing short of extraordinary, and I wouldn't trade them for the world.

But I hope we don't lose something equally valuable along the way.

Learning was once an adventure. Every new concept felt like opening another door. Every difficult problem carried the promise of understanding on the other side. The joy was never in the difficulty itself — it was in the understanding that the difficulty produced.

That joy is still available to us today. Not because we have fewer resources, but because we can choose how we use them. The best learners are not the ones who consume the most. They are the ones who never lose the joy of discovering something new.

May your curiosity stay alive — and may your learning always feel like it belongs to you.

That’s all for now. May your intention be clear and your mind be still. With this quiet wish, I rest my pen and return to the silence.