The key is goodness/badness of advice is a function of the receiver. The internet doesn't give you control over who reads your stuff, so internet advice is safer and less useful than it could be.

The advice "use 'any' if it's too much work to type" is dangerous/bad advice for some developers because they don't have a well tuned definition of 'too much work', and they might not have all the tricks in the toolbox for every situation.

But legacy code or poorly typed libs can be an infinity time suck, and the most pragmatic approach might be to cut your losses, slap an 'any' on it and move on.

A great mentor gives the best (different axis than good/bad or safe/danger) advice for an individual in a specific situation.