The solution
kognise had done a lot of things with computers but always carried a gap: what exactly happens when you run a program? He had most of the low-level pieces yet could not connect them — do programs really run directly on the CPU, how do syscalls work, how do many programs run at once. Outside college there was no comprehensive systems resource, so he sifted through sources of varying and sometimes conflicting quality; after a couple of weeks and almost forty pages of notes, at 17, he wrote the article he wished he had.
The standard approach is a textbook that layers abstractions: fetch-execute, processes, virtual memory, syscalls. cpu.land inverts it: it walks one real action end to end on Linux x86-64, chosen because the kernel is open source and “super easy to research just by reading its source code.” Readers are told to burn in one idea: “everything that seems simple actually is that simple.” Chapter 3 traces execve through do_execveat_common and the binfmt handlers, showing shebangs are a kernel feature, not a shell one, and using git blame to explain why BINPRM_BUF_SIZE doubled from 128 to 256 bytes.
The form does as much work as the content. Chapters are published on cpu.land with an Edit on GitHub link, under the Hack Club organization's repository, and each chapter ends with the question the next chapter answers. Chapter 3 opens with a dare: “Read chapter 3 and I guarantee you will learn something new.” The prose stays playful — “Computers are so cool!” — while the code snippets stay real.
The launch worked. Hacker News gave the post 1,337 points and 307 comments on 9 August 2023. Commenters in their late twenties said they had not known half of it, and a college student said he was recommending the guide to friends because it covered the topics of an operating-systems course. By the September 2026 snapshot the repository held 5.6k stars, 193 forks and 103 commits, and the full text still lives at cpu.land.
What it achieved
Follow one real program through the actual kernel source and refuse the abstractions that hide the path
Why it worked
Tracing one real path through real kernel source makes every claim checkable: readers can open the same files the guide quotes, so trust is earned rather than asserted.
Starting from the reader's actual gap — “what happens when I run this?” — keeps the guide prerequisite-free, introducing each term at the moment the path needs it.
Writing as the person who had the gap, a 17-year-old self-taught coder, kept the curse of knowledge out of the prose; experienced commenters called the care and attention rare.
The explicit dare — read chapter 3 and you will learn something new — gave a skeptical expert audience a testable bar, and the thread confirmed it.
Publishing under Hack Club with an open repository and edit links turned one essay into a maintained asset that kept compounding: 103 commits and 5.6k stars three years on.
What can be applied
When a field's knowledge is fragmented and unequal, write the continuous walkthrough you wished existed: trace one real path end to end, quote actual code, and let verifiability carry the trust
Aftermath
The guide's Hacker News launch on 9 August 2023 peaked at 1,337 points and 307 comments, with readers recommending it to college friends and linking it to operating-systems coursework. The repository stayed open under the Hack Club organization and kept accumulating work — 193 forks, 103 commits and 5.6k stars in the September 2026 snapshot — while the full text remained live at cpu.land, each page still offering an Edit on GitHub link.
FOLLOW THE EVIDENCE