The problem with most of these opinions is that they are absolutes, and therefore by definition many of them are wrong. They could mostly be improved with the addition of "sometimes", "in most circumstances", "depending on the goals of your project", etc. For example:
- "Programmers who don’t code in their spare time for fun [frequently won't be] as good as those that do.
- "Unit testing [may not] help you write good code [in many situations I have encountered]."
- "[Possibly the most useful] “best practice” you should be using all the time is “Use Your Brain” [though for some teams in some circumstances there may be more useful best practices]."
- "If you only know one language, no matter how well you know it, you’re [almost certainly] not a great programmer."
- "Readability is the most important aspect of your code, [depending on your company's goals and method of achieving those goals at this point in time]"
Of course, these are [mostly] opinions, and adding all sorts of disclaimers is [almost] never fun, but opinions stated as absolutes are [almost] always wrong.
- "Programmers who don’t code in their spare time for fun [frequently won't be] as good as those that do.
- "Unit testing [may not] help you write good code [in many situations I have encountered]."
- "[Possibly the most useful] “best practice” you should be using all the time is “Use Your Brain” [though for some teams in some circumstances there may be more useful best practices]."
- "If you only know one language, no matter how well you know it, you’re [almost certainly] not a great programmer."
- "Readability is the most important aspect of your code, [depending on your company's goals and method of achieving those goals at this point in time]"
Of course, these are [mostly] opinions, and adding all sorts of disclaimers is [almost] never fun, but opinions stated as absolutes are [almost] always wrong.