There's a specific kind of bad documentation that I think we've all suffered through.
You search for "what is a goroutine" or "how do database transactions work" and you get one of two things: either a six-page academic paper that assumes you already know the answer, or a tutorial so watered-down it covers nothing real.
What you actually want is someone like that senior engineer at your company the one who, when you finally work up the nerve to ask a dumb question, sits down and actually explains the thing. Not just the what, but the why. Not just the happy path, but the part where you'll get confused at 2am and what to do about it.
I've been building that resource. It's called The Missing Manual.
Here's the pitch in one sentence: it's a free, growing library of developer guides written like advice from a battle-hardened friend who genuinely wants you to understand the thing, not just copy the code.
Some examples of what's in there right now:
- Reading a Stack Trace at 2am — starts with "that wall of text is not an attack, it's a map," then teaches you the four-step method that works in Python, JavaScript, Java, or whatever you're using. Includes the site-packages/ vs your-own-code trick that turns 40-line traces into 2-line ones.
- Go From Zero - covers the basics, but also the deep stuff that most Go tutorials skip: what the GMP scheduler actually does, how escape analysis decides what lives on the heap, why goroutines are cheap in a way OS threads aren't. Mental-model-first, the whole way through.
- Docker Without the Magic - doesn't just show you docker run. Explains what a namespace and a cgroup actually are, so when Docker does something weird, you have somewhere to start.
- Why Is My Query Slow? - the real answer, including EXPLAIN, index cardinality, the N+1 problem, and what "using index" in a query plan actually means vs what you want it to mean.
There are 160+ guides across debugging, databases, infrastructure, networking, APIs, AI/ML, performance, and programming languages, coding playgrounds,quizzes, learning path and games for brain
A few things I deliberately tried to avoid:
- No "In this tutorial, we will..."
- No explaining what you're about to explain. Read the error type and message. Here's what it looks like. Here's what it means. Done.
- No skipping the hard bit. Every good piece of documentation has a moment where the author clearly said "this part is complicated, I'll wave my hands." I tried to find those moments and sit in them longer, not shorter.
- No pretending the path is clean. The stack trace guide has a war story about a teammate who spent 20 minutes reading a trace top to bottom, convinced the bug was deep in the ORM, when it was three lines from the bottom in their own file. The lesson lands better with the story.
The platform itself runs on a Rust back-end (axum + Tantivy full-text search) and a SvelteKit front-end and using Cloudflare's AI Search for more natural language search.
The search actually works and you can type "goroutine leak" or "explain joins" and land where you need to.
It's free. No account required to read. No paywall.
If you've ever had the experience of finally understanding something properly because someone explained it the right way, not just showed you the command, that's what I'm going for.
Drop a comment with a topic you've always wanted explained like this. I'm actively adding guides and the request list genuinely shapes what gets built next.
Tips for reading: jump straight to the phase you need. Every guide is organized into phases and marked with difficulty badges (Beginner → Advanced), so you can skip the sections you already know and focus on what's most relevant to you.
Also, please share your feedback. Every suggestion, correction, and idea helps shape the final product I'm working to build.
