In industry, the prevailing code standards are almost certainly wildly divergent from any sort of Ruby "best practice". In particular, if the goal is to have c

In industry, the prevailing code standards are almost certainly wildly divergent from any sort of Ruby "best practice". In particular, if the goal is to have clear (and therefore somewhat more likely to be robust) code, you're going to see things like the use of single quotes to indicate "this will never be interpolated" or the use of explicit return statements even when "unnecessary" - both of which run afoul of these sorts of highly-opinionated and unconfigurable style enforcers.