> because you know what, if it works, it isn't terrible to use/update and doesn't leak millions in lost revenue then there's no valid reason to spend dev time o

> because you know what, if it works, it isn't terrible to use/update and doesn't leak millions in lost revenue then there's no valid reason to spend dev time on that. Really bad code grinds progress to a halt when developers have to spend all of their time fixing tech debt or working around fragile codebases to get anything done. However, I don't see anything in this code that would match that description. In fact, anyone can take one look at this and know exactly what it does and exactly how to modify it. Counterintuitively, perfectly good code also grinds progress to a halt if developers become too focused on doing things the "right" way instead of shipping reasonable code that works. Developers who get lost pursuing a platonic ideal of the perfect code will be perpetually disappointed inside of real-world constraints. Perfect is the enemy of good. It's definitely not fair to criticize a single snippet extracted from an entire company's code base. It's turning into a cheap way to dunk on a company from the sidelines while ignoring that the company has done a good job of scaling a video delivery platform and community to a massive number of users.