You’re not looking for quick fixes. You’re looking for understanding.
A self-taught developer’s notes on how things actually work. Linux internals, systems programming, and the mindset of a mature engineer — no tutorial hell, no corporate noise.
Linux internals →
Kernel, memory, processes, syscalls. What the system actually does when your code asks it for anything.
Systems programming →
Allocators, I/O, signals, linking. The layer where abstractions leak — and you need to know why.
Engineer’s mindset →
Hypothesis-driven debugging, reading other people’s code, when DRY hurts. How you think when you get it, instead of guessing.
I write for developers and self-taught programmers who want to understand how code and systems work.
I’m self-taught myself — no formal specialization, but I run Arch every day and I dig until I understand. If a tutorial leaves you asking “but why does that work?”, you will find topics to explore further here.
New articles, straight to your inbox
When they drop — no spam, no growth hacks. Unsubscribe in one click.