What exactly happens when a process touches a bad address. From the MMU and page table through the kernel page fault handler to core dump analysis in gdb — null deref, stack overflow, use-after-free.
Anatomy of a Segfault — From MMU Through Kernel to gdb Core Dump Read Post »
Your terminal takes 800 ms to start. Bash loading anatomy, lazy loading version managers, completion caching, PS1 without synchronous git status — and how to drop to 50 ms without compromises.
.bashrc — Anatomy of Shell Startup and Performance Optimization Read Post »
Anatomy of two Linux I/O models. epoll vs io_uring, readiness vs completion, syscall overhead, SQPOLL — and when reaching for io_uring instead of an event loop actually pays off.
epoll vs io_uring — When the Event Loop Isn’t Enough Read Post »
DRY has become a dogma that destroys more code than it saves. When duplication is the correct architectural decision — and how to recognize the moment when chasing “Don’t Repeat Yourself” stops being engineering.
The DRY Myth — When Code Duplication Is the Correct Architecture Read Post »
Skip the container abstraction layer. Enforce CPU, memory & I/O limits directly via cgroupfs — zero daemon overhead, no OCI ceremony. A deep dive into cgroups v2 on Arch Linux.
cgroups v2 as a Native Runtime Isolation Primitive — No Docker Required Read Post »
Reading other people’s code separates juniors from seniors. Most developers read code like a novel — and get lost. Learn to read systematically: entry points, callsites, grep before LSP, git as a navigation tool.
Reading Other People’s Code — How to Do It Faster Than You Wrote Your Own Read Post »
fork() in Linux isn’t just process copying. It’s one of the cleverest kernel mechanisms — Copy-on-Write, shared file descriptors, inherited mutexes. Find out what really happens under the hood.
Linux fork() — how it works, copy-on-write and zombie processes Read Post »
Debugging like a developer means thinking, not guessing.
Most engineers debug by trial and error — that’s gambling
with production code. Learn how to form hypotheses, find
root causes, and stop chasing symptoms.
Why Most Developers Debug Wrong — Debugging Like a Developer Read Post »