The Perils of Complaining About Legacy Code
Description
A screenshot of a tweet from user Zoid Kirsch (@ZoidCTF). The tweet is displayed in white text on a black background. The text recounts a personal anecdote: 'While working on Dota 2 in 2012, several engineers at Valve joined the team to help. I was working on something that used a lot of Window's API calls and I was grumpy and said "ugh Windows API sucks." One of the engineers said, "You know, I wrote USER.DLL, I was 19 at the time."'. This story serves as a classic cautionary tale for developers. It humorously highlights the awkward and humbling experience of criticizing a piece of technology without realizing one is speaking to its original creator. For senior engineers, it's a deeply relatable 'foot-in-mouth' moment that evokes empathy for the authors of legacy systems, who often worked under immense constraints and at a surprisingly young age. The anecdote is a piece of tech folklore, reminding developers that even the most frustrating legacy APIs were built by brilliant people
Comments
17Comment deleted
This is why you always run `git blame` on a legacy system before you actually blame it out loud
Reminder: before you flame a 30-year-old API in code review, check whether the diff author also shipped the original DLL - back when you were still figuring out strcpy
The only thing worse than debugging USER.DLL is realizing you just called it garbage to the face of the prodigy who wrote it before they could legally drink. That's like complaining about React's virtual DOM to Dan Abramov, except this guy built Windows' entire user interface layer while you were still figuring out bubble sort in CS101
Nothing quite like complaining about an API's design choices only to discover you're talking to the 19-year-old who wrote it while you were still figuring out Hello World. USER.DLL has been handling window messages since Windows 1.0 - turns out the real legacy code was the friends we made along the way, and some of them are standing right behind you
Nothing humbles a grizzled dev like dunking on Windows API to the 19-year-old who authored USER.DLL - talk about meeting your tech debt's architect
Win32 is what happens when an ABI gets preserved in amber; griping about it to the author of USER.DLL is the IRL version of git blame pointing to a single 90s commit you can’t refactor because half the world still depends on it
Careful yelling "Win32 sucks" - the person who crammed your feelings into wParam/lParam might be in the standup; ABI stability means their teenage decisions still ship your game
It’s a small world. Comment deleted
Yeah, like Valve was founded by ex-MS people in Seattle ... Comment deleted
aren't they had some random delivery guy Comment deleted
Wait, someone actually worked on Dota? Comment deleted
https://dota2.fandom.com/wiki/Shitty_Wizard Comment deleted
I've chatted quite a bit with Finol during 2nd half of 2012, back then he could handle most of the reports manually Comment deleted
and left as lead of kernel team Comment deleted
blame everything built on top of idTech 2😁 Comment deleted
Man i lost this legendary video long time ago Comment deleted
this explains... so much Comment deleted