Community
Guides, notes, and the writers behind them — everything worth exploring.
What REST really means — resources, HTTP methods, status codes, headers, auth, versioning, pagination, and designing an API people enjoy using.
Curated guide · updated 2026-07-14
Debugging as a repeatable method, not luck — reproduce, isolate, form hypotheses, read the error, bisect, and the tools that make it faster.
Curated guide · updated 2026-07-13
Git from first principles — the mental model, the everyday commands, branching, merging, undoing mistakes, and a sane workflow.
Curated guide · updated 2026-07-12
How to write docs people actually read — knowing your reader, the four documentation types, structure, examples, and keeping docs alive.
Curated guide · updated 2026-07-11
A repeatable system for learning technical skills that actually stick — spaced repetition, projects, notes, and avoiding tutorial hell.
Curated guide · updated 2026-07-10
A sensible way to lay out a codebase — folders by feature, separating concerns, config, naming, and structure that scales as the project grows.
Curated guide · updated 2026-07-09
The Linux a developer actually uses daily — the shell, files and permissions, processes, pipes, and the commands worth memorizing.
Curated guide · updated 2026-07-08
Building UIs that stay maintainable — component boundaries, state, consistency, accessibility, and design decisions your future self will thank you for.
Curated guide · updated 2026-07-06
The complete OSI reference — every layer, its protocols, devices, headers, addressing, security, and how it maps to TCP/IP. One page, everything.
Curated guide · updated 2026-06-17
The two transport protocols compared in full — how each works, when to use which, headers, reliability, security, and where QUIC/HTTP-3 fits.
Curated guide · updated 2026-06-17
The 4-layer model the internet actually runs on — each layer, its protocols, how it maps to OSI, encapsulation, a real web request, and why it beat OSI.
Curated guide · updated 2026-06-17
Stuck and can't solve even one problem? This is the gentle, from-zero guide to how problem solving actually works — solve by hand first, then code. A ~22 minute read.
Curated guide · updated 2026-06-17
