✳flâneur — a map of the web's best reading

Learning and reviewing system internals: tactics and psychology — Jack Vanlightly

jack-vanlightly.com · 3,328 words · saved by 1 readers

Every now and then I get asked for advice on how to learn about distributed system internals and protocols. Over the course of my career I've picked up a learning and reviewing style that works pretty well for me. To define these terms, learning and reviewing are similar but not the same: Learning about how a system works is the easier of the two. By the means available to you (books, papers, blogs, code), you study the system to understand how it works and why it works that way. Reviewing a system requires learning but also involves opinions, taking positions, making judgments. It is trickier to get right, more subjective, and often only time can show you if you were right or wrong about it and to what degree. We all review systems to one degree or another, even if it's just a casual review where the results are some loosely held opinions shared by the coffee machine. But when it comes to sharing our opinions in more formal contexts, an architecture meeting, a blog post, a conference

Every now and then I get asked for advice on how to learn about distributed system internals and protocols. Over the course of my career I've picked up a learning and reviewing style that works pretty well for me. To define these terms, learning and reviewing are similar but not the same: Learning about how a system works is the easier of the two. By the means available to you (books, papers, blogs, code), you study the system to understand how it works and why it works that way. Reviewing a system requires learning but also involves opinions, taking positions, making judgments. It is trickier

Explore this link on the map →

saved by

related reading