(I might get a bit crucified for saying this, but I think it’s good advice, so I’ll say it.)

If you are a programmer, I suggest you only take programming advice from those who build good software themselves.

This doesn’t mean you should only take advice from open source contributors, or famous programmers only (there are great programmers out there that only build at work and can’t publish what they build). But what I suggest is taking a wide berth from advice provided by programmers that do little building themselves.

When someone suggests using X or not using Y or doing Z, I suggest you ask the advisor for examples of how that impacted the craft/experience of what they build. If you’re not impressed, nor convinced, move on. This is particularly useful for filtering out negative advice towards a certain tool or approach.

There seems to be a significant amount of programmers out there that are more invested in a viewpoint than in their own process of becoming a builder of great software. Their advice can be a great hindrance.