> we should instead grow the developers to understand these different approaches as opposed to labeling half of the language "bad practice". > As I said in ano

> we should instead grow the developers to understand these different approaches as opposed to labeling half of the language "bad practice". > As I said in another comment. Ruby was built to have multiple ways of doing the same tasks and criticizing it for this is... pointless. Agreed 100% with this take. If I only wanted 1 way to accomplish something no matter how inelegant it might be in that context, I would use Python. I choose Ruby specifically because of how expressive it is. It makes it a bit tougher when working in a team with 2 or more opinionated devs, ie. "should we use more functional or more OO approaches to solve a problem" but this is a culture and communication issue, not a language problem. Having a good rubocop setup and staying within the confines of your agreed upon ruleset is a good start. For example you can use rubocop to enforce dissallowing `unless !condition`, then it's just not an issue anymore - these kinds of issues dissapear before code even makes it to review.