You don't realize you've crossed the threshold until it's too late.
Five hours later, you're seven tabs deep in a LWN.net discussion about kernel scheduler anomalies. You've read the original git blame for a line changed in 2005 by a maintainer who now runs a goat farm in Vermont. You understand, for a brief, terrible moment, why the C standard library does what it does with memcpy on non-overlapping blocks.
The deep truth: Every layer is a lie that works well enough. Every protocol is a compromise ratified at 2 AM in a hotel bar in 1994.
So keep pulling threads. Keep reading the dmesg output. Keep being the one who knows why the silence between keystrokes isn't empty—it's interrupts, scheduling jitter, and a million cycles of a CPU that doesn't care about your mortal concept of "now."
You don't realize you've crossed the threshold until it's too late.
Five hours later, you're seven tabs deep in a LWN.net discussion about kernel scheduler anomalies. You've read the original git blame for a line changed in 2005 by a maintainer who now runs a goat farm in Vermont. You understand, for a brief, terrible moment, why the C standard library does what it does with memcpy on non-overlapping blocks. geek crack
The deep truth: Every layer is a lie that works well enough. Every protocol is a compromise ratified at 2 AM in a hotel bar in 1994. You don't realize you've crossed the threshold until
So keep pulling threads. Keep reading the dmesg output. Keep being the one who knows why the silence between keystrokes isn't empty—it's interrupts, scheduling jitter, and a million cycles of a CPU that doesn't care about your mortal concept of "now." You understand, for a brief, terrible moment, why