Continuous Learning

Definition

Deliberately maintaining and extending technical judgement. The difficulty is not access to material but selecting what is worth the attention.

What is worth learning deeply

Fundamentals, which do not expire. Distributed systems theory, queueing behaviour, consistency models, networking, data modelling, security principles. Knowledge from twenty years ago in these areas remains correct and transfers to every new technology.

Failure modes, which recur across technologies. Cascading failure, thundering herd, split brain, hot keys, dual writes. Understanding the mechanism means recognising it in a system you have never seen.

Your own domain. Deep knowledge of the business produces better architecture than broad knowledge of technology, and it is much less commonly held.

What is worth learning shallowly

Current technologies. Enough to know what exists, what problem each solves, and when it might apply. Depth here has a short shelf life and should be acquired when a specific decision requires it.

The most valuable sources

• Incident reports, especially other organisations' published ones. The densest available source of how systems actually fail, and free.
• Engineering blogs from companies operating at scale, read critically — their constraints differ from yours, and reasoning by analogy from them is a common error.
• Foundational papers. A handful — on consensus, on distributed storage, on large-scale data processing — explain most of what came after.
• Reading code, particularly of things you use.
• Operating things yourself. On-call teaches what no reading does.

The habits that work

• Build something with it. Reading about a technology produces the illusion of understanding; using it produces the real thing, including the failure modes.
• Write about it. Explaining forces the completeness that reading lets you skip.
• Learn from failure, yours and others'. Keep a record of what you were wrong about — it is how pattern recognition gets calibrated.
• Deliberately explore outside your area, since transferable insight comes from elsewhere.

What to avoid

Chasing every new technology, which produces breadth with no depth and a tendency to adopt novelty for its own sake. And confusing familiarity with understanding — having read the documentation is not the same as knowing how it fails.

Interview question

"How do you decide what technology to learn deeply and what to know only superficially?"