Yeah, the annoying thing is the people who I generally have found to be the worst about stuff like this are old school Senior C developers, who still program like it’s 1987 and we have to fit everything into 4K of RAM.
Fortunately there’s nothing like that in my code base, I just run into stuff like that periodically when I’m digging around in other team’s server code looking for something.
My personal code readability axe to grind is nested complex ternary operators.
Every now and then I’ll see something like this
return (checkFormatType(currentObject.type==TYPES.static||currentObject type==TYPES.dynamic?TYPES.mutable:TYPES.immutable)?create format("MUTABLE"):getFormat(currentObject));
And I have a fucking conniption because just move that shit into a variable before the return. I get it when sometimes you just need to resolve something inline, but a huge amount of the time that ternary can be extracted to a variable before the ternary, or just rewrite the function to take multiple types and resolve it in the function.
Fully agree. Honestly there’s a few subjects where this kinda logic comes up and I get annoyed. Like it’s fine to not be perfect, but don’t pretend that you aren’t perfect, or that your choices are somehow ‘good’ when they aren’t, just because you don’t like the realization.
Yeah but this also results in the site receiving less money from ads, also hurting them in the long run. Really the solution is to pay for the services you enjoy, and acknowledge the age-old “if the service is free, you are the product”.
The problem is the obscenity exception is also used for things like preventing someone from walking around a public park with a giant sign covered in gore porn. Something like that I think is obviously pretty okay to ban, but clearly it gets misused for a lot of homophobic/transphobic type stuff.