I feel like this list has been designed in such a way that it is not possible to create any code, without implementing an example from the list.
When you make a list this long, you're attempting to cast a wide net over most conditions, if not trying for total coverage by including catch-all buckets.
Meanwhile, it feels slightly impossible to ask anyone to write code at all, without having them complain about something.
The only lesson I can glean from this is that every project requires a compromise of combining abominations with idealized perfection, and that transitory human moods and emotions have more effect on programming tastes, than actual practicality.
This is the case with most such lists of verboten practices. It's good to know the general rules, but it's also important to know when your situation justifies breaking them. Competency is all about good judgment.
When you make a list this long, you're attempting to cast a wide net over most conditions, if not trying for total coverage by including catch-all buckets.
Meanwhile, it feels slightly impossible to ask anyone to write code at all, without having them complain about something.
The only lesson I can glean from this is that every project requires a compromise of combining abominations with idealized perfection, and that transitory human moods and emotions have more effect on programming tastes, than actual practicality.