[mid-kid]

Yandere Simulator's case was unique. You're right that people were angry at the guy in general, and he was also quite the internet clown. But it was the first time I've seen so many people who don't program suddently have an oppinion on what good code is or isn't. When asked, they couldn't even explain why. I assure you, half of those videos are filled to the brim with milquetoast examples that I really don't feel constitute as bad code. This thankfully doesn't happen every day.

I really don't enjoy the discourse regarding "code cleanliness". A lot of the time it's just about "I prefer writing things this way" rather than the code actually being slower/harder to read/maintain/whatever. There's a billion ways to write something and none of them are outright wrong!

[mrguyorama]

The reason Yandere dev got so much vitriol (besides generally being a gross human being) is that he loudly proclaimed that his code was great, and he was the best programmer, while doing things like making trivial O(n^2) loops in a game that ran terribly precisely due to those things. He also constantly sought free work from fans that he could profit off of, and even when people offered to help him make his code not atrocious, he pushed them away and was a toxic dick about everything.

He's the exact kind of "I'm the best" that every professional has run into before and cleaned up after.

This wasn't some amateur doing his best with limited resources to give a fun experience to the world, this was a hateful, angry person earning $3500 a month in patreon subscriptions begging for free 3D models from his fans, berating them for giving him free 3D models that "weren't good enough", and refusing to spend a single dime of that revenue on fixing, finishing, polishing, improving etc his abortion of a video game.

[KronisLV]

> I really don't enjoy the discourse regarding "code cleanliness". A lot of the time it's just about "I prefer writing things this way" rather than the code actually being slower/harder to read/maintain/whatever.

Agreed, that's why I think there's arguments that can be made in favor of both DRY/WET, as well as SOLID/CUPID/whatever, even when those are in contradiction with one another, as well as more freeform approaches and KISS/YAGNI. Whatever works for each team and project.

> There's a billion ways to write something and none of them are outright wrong!

However, when your app is doing 2000 DB calls to render a list with some data because of the N+1 problem, I'd say that the code is definitely written wrong. When you need to jump around 20 different files across 6 layers of abstraction that could have easily fit into half of that, then the code might definitely be wrong and unmaintainable.