What we can really learn (or remind ourselves) is that code “quality” is rarely representative of company value.
If the Twitch codebase hadn't leaked, how many people would have known that their naughty-word-blocker was implemented in a less than perfect fashion?
Also, any large codebase will develop some wharts due to circumstances you can't see when simply reading the code.
The way I see it, programmer perfectionism comes from learning - the projects you do for yourself, early on, are small enough that you can hit perfect trade-offs on your limited needs, and you aren't under time pressure. You quickly learn you can achieve near-perfection - a lesson which stops applying when working with any nontrivial codebase at work.
(Not sure where I was going with this)
You can add a lot of spice by propping up the care with some nicely tuned turbo, pedal behavior and cooling that is sufficient for just a few accelerations. Most people will never find out the difference.
This snippet is not the biggest problem with the twitch leak, I spooled through the terraform and a lot of it is awful. But it obviously works for them.
I had a overwhelming realisation that code quality really doesn’t matter, I spend a lot of time making my code clean and easy to understand- and that might improve _my_ ergonomics. But realistically my company is not bigger than twitch and if they can operate without major problems with this code then obviously it doesn’t matter.