I'm Still Happy With It

Dad walks in thinking you're having fun, but you're just crying while watching benchmark videos of a $1,500 gaming rig that'll spend most of its life compiling code and running Docker containers. You tell yourself it's for "productivity" but really you're just procrastinating on actual work by obsessing over whether the RTX 4080 will give you 3% better performance in a game you'll install, play for 20 minutes, then never touch again. The PC building rabbit hole is real—you start researching one component and suddenly it's 3 AM, you've got 47 browser tabs open comparing RAM timings, and you're $800 over budget. But hey, at least your IDE will launch 0.2 seconds faster, right?

The GPU and CPU oligopoly in its natural habitat. Intel, Nvidia, and AMD standing there like aristocrats who just realized they could charge whatever they want because consumers literally have nowhere else to go. "Should we improve our products?" "Nah, they'll buy them anyway." And they're absolutely right. You need a graphics card? That'll be your kidney plus shipping. Want a competitive CPU? Pick from these three families and pray one of them isn't on fire this generation (looking at you, Intel). The free market is supposed to breed competition, but when there are only three players in town, it's more like a gentleman's agreement to keep prices astronomical while we all pretend the next generation will be "revolutionary." Spoiler: it won't be.

When Nintendo announces a €459.99 Switch 2? Meh, too expensive. But slap a Steam logo on a handheld gaming PC for €419? Take my money immediately! The classic "I hate your overpriced product but will happily buy this slightly less expensive alternative that does basically the same thing but feels more justified because I can also use it to pretend I'll do actual work on it someday." The Steam Deck: where we convince ourselves we're making a practical purchase while still blowing our rent money on games.

Let's be real: if you held CDs and DVDs by the edges like a civilized human being, you were probably the same person who actually wrote documentation and used meaningful variable names. Meanwhile, the rest of us were out here fingerprinting the data side like we were booking suspects at a police station, wondering why our burned copies of Linux ISOs kept failing the checksum. The "filthy animal" crew also definitely had that one scratched-to-hell disc that somehow still worked 60% of the time, and we'd spend 20 minutes cleaning it with our shirt before every use. Different times, same chaotic energy we bring to production deployments today.

Dracula fears the sun. Superman fears kryptonite. PC builders? They fear the forbidden bundle of doom that is the motherboard cable spaghetti. You can bench 300 pounds, survive on coffee and Stack Overflow, but the moment you see POWER SW, RESET SW, HDD LED, and POWER LED staring back at you with their tiny connectors and tinier labels, suddenly you're questioning every life choice that led you here. The manual is useless, your fingers are too big, and you're 90% sure you're about to fry a $500 motherboard because you can't tell positive from negative on a 2mm connector. It's the final boss of PC building, and it never gets easier.

The perfect metaphor for that moment when a dev who's been happily coding in their comfortable high-level language suddenly discovers the raw power of C++. It's like watching someone who's been driving an automatic transmission their whole life suddenly discover they can control EVERY gear manually. "You mean I can manage my own memory? And directly access hardware? And create memory leaks that will haunt my nightmares for years? SIGN ME UP!" The wide-eyed "WOW" is that brief moment of amazement before reality sets in and they're debugging pointer arithmetic at 3AM while questioning all their life choices.