Learning then vs now
Sometimes I feel old when I look at how people learn today. I'm not that old, but I'm closer to my 50s than I'd like to admit.
Earlier in my career, learning mostly meant books, conferences, articles, and long conversations with other engineers. If you wanted to learn something, you went looking for it. That felt normal to me for a long time.
A well-intended mistake
A few years ago, I was trying to find a sustainable way to encourage learning on our engineering teams. We already sponsored conferences and online training, but I wanted something with more staying power.
That's when I thought about books. I remembered how much I used to enjoy them, and how they let you sit with an idea for longer than short content usually does. So I worked with HR, got a budget approved, and bought a copy of The Pragmatic Programmer for everyone.
Different ways to learn
I got some thank-yous, but the most common reaction surprised me: "Why a book?" That was the moment I realized I had projected my own learning style onto everyone else.
I started asking what people actually preferred. The answers were clear. Some wanted audiobooks. Others preferred videos, summaries, or walkthroughs. Some wanted depth, others wanted only the core idea. Not everyone disliked the book, but the variation in preferences was impossible to ignore.
Rethinking assumptions as a leader
In retrospect, I should have asked first. The intent was good, but the execution ignored individual differences.
I stopped repeating that approach for new hires and started listening earlier. Now I try to support how each person learns, even when it's different from how I would do it myself.
That experience pushed me to think more broadly about learning in our profession, not just how people learn, but also who they think learning is for.
Learning beyond employer support
There's a related tension I still find uncomfortable. Some developers believe learning should mostly happen on company time, funded by the employer.
I agree that companies should invest in learning, and good ones do. But it's rarely enough to cover everything the market may ask from you later. Technologies shift, priorities change, and what your company needs today may not match what you'll need in your next role.
The market reality
What I still find difficult is seeing people slowly shift into the assumption that what they know today is enough. It rarely looks like resistance. It usually looks like comfort.
They know the system, they do their work well, and learning becomes optional unless the company organizes it. On its own, that isn't a moral failure. People have lives, constraints, and finite energy.
It becomes harder when learning is framed only as something the company owes, rather than a shared responsibility. The market often rewards readiness, not intent. When skills become urgent, companies frequently hire for them instead of waiting for internal catch-up.
That doesn't mean everyone should study every night or sacrifice personal life. Many people can't, and that's understandable. But when you have to re-enter the market, context matters less than capability. The market evaluates what you can do now.
Learning as a long-term loop
What I've learned over time is that learning never really ends in this profession. It comes in waves depending on where you are in your career and in your life.
I don't think the goal is to learn everything. The goal is to stay in motion: choose a few priorities, let others go, and adjust as the market changes. The list doesn't get shorter. It changes shape.
The people who seem most resilient over time are not necessarily the ones who know the most. They're often the ones who stayed comfortable with learning itself.
Over time, I've come to see learning less as a milestone and more as a practice. It stays useful when you keep exercising it, even in small ways.
Like any other practice in this profession, it fades when you stop using it.
- Patrick