Learning Tech Efficiently When You Have No Timeby@simon-gerber
158 reads

Learning Tech Efficiently When You Have No Time

by Simon GerberFebruary 28th, 2019
Read on Terminal Reader
Read this story w/o Javascript
tldt arrow

Too Long; Didn't Read

I’ve had a few¹ people ask me how I seem to learn technologies so quickly when I’m always complaining that kids are a temporal black hole that suck in all available free time and mental capacity. It was an interesting question! It challenged me to actually stop and think about whether I do anything specific when learning about new things. I realized that I did. Apparently I do have a personal methodology.

Companies Mentioned

Mention Thumbnail
Mention Thumbnail
featured image - Learning Tech Efficiently When You Have No Time
Simon Gerber HackerNoon profile picture

Personal tips for learning new languages, frameworks and technologies rapidly on a strict time budget

I’ve had a few¹ people ask me how I seem to learn technologies so quickly when I’m always complaining that kids are a temporal black hole that suck in all available free time and mental capacity. It was an interesting question! It challenged me to actually stop and think about whether I do anything specific when learning about new things. I realized that I did. Apparently I do have a personal methodology.

The approach I outline below is what works for me, personally. Perhaps it will work for you as well. There’s no harm in trying, right?


At least a little time. Not much, but a little. Say 20–30 minutes, 2–3 days a week².

Some weeks I struggle to even find that much time to set aside! It can be hard. Especially with kids. Or if, you know, you want to have a life outside of work. But there are always ways. Ultimately it comes down to prioritization. If you really need or want to learn something, this is really probably the bare minimum time investment.

We’ve just established that there is no free lunch. I lied. Actually no, I didn’t. I may have implied there was a solution to learning when you have no time, but there isn’t. You do need a little bit of time. Just a little. But it does change the question we need to ask ourselves to, “How to invest the minimum time possible to get the maximum return in knowledge?

Different people have different learning preferences. Visual, aural, verbal, physical and so forth. I am a verbal learner — so the methodology I shall soon present is geared towards verbal learning and may not work for you. Given that, it’s doubly important to first discuss what our learning goals are.

With only a small amount of time up your sleeve your primary goal should not be to learn a new tech in-depth. You won’t have time to become a master or an expert. ‘10,000 hours of practice’ may be a vast oversimplification, if not an outright myth, but an hour a week, broken across a few days, won’t take you far.

So: Your primary goal should be to translate ‘unknown unknowns’ into ‘known unknowns’.

A metaphor that helps me is to think of someone dumping a 1000 piece jigsaw puzzle on your desk. There’s no box. You don’t know what the picture is. If you were asked, “Tell me what that’s a picture of”, you would likely handle the task in a very different way compared to if you were just asked to ‘assemble the puzzle’.

If your goal is just to assemble the puzzle you don’t even need to know what the picture is. You might find the corners, then find the edges, group them by shade or color, brute-force edge pieces until they fit, group the inside pieces by shade or color, and so-forth. At some point you’ll figure out what the picture is, but it may take you a while to get to that point.

On the other hand, if you’re just asked, “what is it?”, there’s no need to waste time assembling the puzzle. Just flip all the pieces face up, look for bits that seem related, try to find things that seem familiar.

Translated back into the technical domain, focus on ‘what’ over ‘how’. You can learn the ‘how’ on an as-needed basis. For example, if you know ‘Technology X’ has ‘Feature Y’, and ‘Feature Y’ is useful in ‘situation foo’ — when you hit ‘situation foo’ in your work then you can work backwards from there.

General Tips

  • Learn to speed read. The gist of it is that eye movements slow down your reading. Learning to speed read is about learning to absorb ‘chunks’ of text without moving your eyes. The nice thing about practicing speed-reading is that even if you don’t ‘chunk’ all the time when reading technical articles, the practice will speed up your regular reading.
  • Forget about video, forget about audio. Podcasts, conference talks and online lectures are good for slowly absorbing detailed information. But in my personal opinion, text is a superior vector for fast, targeted learning.
  • You can read much faster than someone else can talk, even if you play the video/audio at 1.5x speed. This is especially if you put in even a little effort learning to speed read.
  • You can ‘fast-forward’ text. Skip the boring bits, the things you know already or aren’t immediately relevant. Well, sure you can fast-forward video and audio, but you generally don’t know what you’re missing.
  • Lean on the fact that technology is evolutionary — the ‘new’ technology you are using is probably actually an old or rediscovered technology with a few tweaks or modifications. I cover this in more detail in my article on learning as a super-power. Ergo — if you already know the technology the ‘new thing’ is based upon, it will be quicker to learn.

  • Intersperse targeted learning with general reading about architectural concepts and programming paradigms. General knowledge helpsfill in the gaps about why and where you would want to use ‘Technology X’.


  1. Hit up the official website (if any) and look for the main features, or ‘why choose us’ type articles. Where comparisons are made to othertechnologies, take note of what they are.

  2. Hit up the official documentation — but specifically look for sections that give you a condensed overview of the main features. Skim the ‘what’s new’ section; read the Table of Contents; hunt down any ‘quick start’ guides
  3. Google for ‘Technology X vs. Y’ articles. See Step 1 for technologies to compare against.
  4. Tip: Let google autocomplete for you if, you don’t know what technologies it should be compared to.

  5. Read _All The Books_³. But not all of each book. Skip the code samples, you can come back to them later when you need to actually use that feature.Skim through familiar material. Don’t read every word of every sectionPay close attention to summary diagrams, section headers and summary chapters.

  6. When the words you are reading stop making complete sense, do not stop reading or slow down right away. Try to push on a littlefurther and get at least a general sense of what lies ahead of you. Then switch to another book (usually the most popular technologies will have multiple books if they’re more than a few years old) and repeat step 4. Since you are now familiar with the material, you’ll probably get a little further — and reading the same thing phrased differentlyhelps it sink in.

Plan B

What if there are no books and the documentation is poor? Tricky! Personally, if I have any choice in the matter, I’d probably not choose a technology that wasn’t moderately well documented. If you don’t have any choice follow the general tips. Look for as much similarity as you can between what you’re trying to learn and precursor tech, then look for ways to understand how it differs.


Now it’s time to apply what you’ve learnt!

But you won’t know how, because you were skipping code samples and only skimming documentation.

The trick is — if this technique is going to work for you — by now you have a mental map of how the technology is supposed to work, what it can do for you, and what special or unique features it has to differentiate it from what you’re currently doing. So although you don’t initially know to directly apply what you’ve learnt, you’re pretty sure you remember a section of the documentation that talked about ‘Feature X’ which would be really useful right now.

Now, then, is the time go back and read the relevant detailed documentation or code samples.

That’s pretty much it! Read as much as you can, as quickly as you can. Focus on the class of problems the tech is meant to solve and key features and differentiators. This technique works really well for me, I have successfully applied it to learning frameworks like Spring, Play, Ktor; languages like Kotlin, Scala, Haskell, Elixir; middle-ware like RabbitMQ and Kafka; and other miscellaneous tools like Puppet, Hashicorp Consul and similar.

I hope these tips work for you, too — and if you’re happy to leave feedback, I’m always interested in hearing about your techniques for fast learning.

[1] Specifically, two

[2] In my case, this is a function of the length of my commute and the a probability of getting a seat.

[3] Paper tech books are expensive, in Australia at least, but if you are happy with electronic copies those are often very much cheaper. But really what you want to do is convince your workplace to provide you with a subscription as part of a training budget.