How to learn a new technology fast, depending on how you learn
Updated
Short answer
First know your way in. Hands-first learners should break something small immediately and read the documentation only when stuck; map-first learners should spend an hour on the shape of the system before touching it. Then decide what the technology is to you — a tool to finish a job, or a craft to master — because that sets how deep to go.
There are two ways in
- Hands first. You learn by doing something with it, breaking it and fixing it. Reading the manual first feels like homework and does not stick.
- Map first. You want the shape of the system — what the parts are and how they connect — before you touch a switch. Diving in without it makes you anxious and slow.
Neither is faster in general. Each is much faster for the person it suits, and the most common reason people feel slow at learning tech is being taught the other way.
If you are hands-first
- Pick the smallest real thing you want it to do. Not the tutorial project — yours.
- Build that badly, today.
- Read documentation only for the exact thing you are stuck on.
- Once it works, read the overview. It will finally make sense.
If you are map-first
- Spend an hour on the architecture: the main concepts and how they relate. Draw it.
- Find the one concept everything else depends on, and understand that properly.
- Then do a guided example, checking it against your map.
- Only then build your own thing.
Tool or craft?
If technology is a tool to you, stop as soon as it does the job — depth you will not use is time you did not need to spend. If it is a craft, the making is the point, and going deeper into one field for years pays more than skimming many.
Master of Technology reads both lines — how you get in, and what technology is to you — and writes a book on keeping pace with it to your answer.
Questions people also ask
- What is the fastest way to learn a new programming language or tool?
- The way that matches how you learn: build something small immediately if you are hands-first; understand the model first if you are map-first.
- Should I learn many tools or master one?
- If technology is a tool to you, learn enough of several to get the job done. If it is a craft, depth in one field compounds.
- How do I keep up when technology changes so fast?
- Learn the slow-changing foundations well, and treat each new tool as a variation on them rather than a fresh start.
Technology
Have Master of Technology written for the way you work.
Twenty-one scenes, about eight minutes, no account. You see your reading and your contents page before you pay. £9.99, delivered as a PDF.