The questions you ask before you pick a course.
Why learn Go. Which papers matter. How distributed systems maps to system design. Long reads, one question each, and every one ends in a course.
read the guidego foundations9 min readWhy Learn Go in 2026: The Honest Case for the AI Era
Is Go worth learning in 2026? What Go is for, what it deliberately leaves out, where it runs the industry, and why a language built for reviewers is the right language when a model writes the first draft.
read the guideclaude code9 min readClaude Code for Working Engineers: What the Tutorials Skip
A Claude Code tutorial for developers who already ship software. The agent loop, plan mode, CLAUDE.md, permissions, and the habits that separate a productive session from an expensive one.
read the guidedistributed systems in a day9 min readDistributed Systems Is the System Design Course, Taught Properly
Every system design interview question is a distributed systems question in disguise. What the interview actually tests, why most system design courses skip it, and a lesson-by-lesson map from first principles to the whiteboard.
read the guidepapers every engineer should know10 min readWhy Engineers Should Read Software Papers, and the Ten to Start With
The computer science papers worth reading as a working engineer, why they matter more now that a model can write the code, and how to read one in an hour without a PhD.
