Working in technology means the material keeps changing. Tools are replaced, practices shift, and there is always more to learn than time allows. Managing that sustainably is less about working harder and more about deciding deliberately where attention goes.
Accept that you cannot learn everything
The volume of available material is effectively unlimited, and trying to keep up with all of it produces a shallow familiarity with many things and competence in none. A more useful approach is to hold a small number of areas deliberately:
- Depth in one or two areas central to your work
- Working knowledge of a few adjacent areas you touch regularly
- Awareness only of everything else — enough to recognise when it is relevant
Deciding what belongs in the third category is as important as choosing the first.
Protect blocks of time
Technical work needs uninterrupted stretches. Being interrupted every ten minutes means never reaching the state where difficult problems become tractable.
- Block time in the calendar for focused work and treat it as a commitment
- Close email and chat during those blocks rather than relying on willpower
- Batch shallow work — replies, admin, small requests — into defined windows
- Protect whichever part of the day you concentrate best for the hardest task
Prioritise by consequence
Urgency and importance are different things, and most people default to urgency. Before starting something, it is worth asking what actually happens if it is not done today. Much of what feels pressing turns out to be someone else's preferred timing rather than a genuine deadline.
Learn by building
Passive consumption — courses, videos, documentation — creates a convincing impression of progress that does not survive contact with a real problem. The reliable test is whether you can build something without following along.
A pattern that works:
- Learn just enough to start
- Build something small that does not quite work yet
- Return to the material for the specific thing blocking you
- Repeat
This is slower at the start and considerably faster overall, because the knowledge is attached to a problem rather than floating free.
Escaping the tutorial loop
Finishing a tutorial and immediately starting another is a common trap. The material is well-structured, progress feels steady, and nothing is actually being retained. Breaking the loop usually means deliberately building something the tutorial did not cover — adding a feature, changing the data source, deploying it somewhere.
Keep notes you will actually return to
Write down what you learn in your own words, particularly solutions to problems that took a while. Over time this becomes more useful than any external reference, because it is indexed by the problems you personally encounter.
Keep it simple. An elaborate system becomes its own project; a plain searchable folder of text files is usually enough.
Review periodically
Every few months, look back at what you have spent time on and whether it moved you toward anything you care about. Interests drift, and goals set a year ago may no longer be the right ones. The point is not to enforce the old plan but to notice when it has quietly stopped applying.
Sustainability matters more than intensity
Learning consistently for a modest period most days outperforms occasional long sessions, both for retention and for not burning out. Rest is part of the process rather than time taken from it — difficult problems frequently resolve after a break rather than during another hour of effort.
Progress in this field is slow and mostly invisible day to day. It becomes obvious only looking back several months, which is a good reason to keep some record of where you started.
