Learning from the mistakes of the less experienced is an interesting tease. I would be happy to hear some expansion of this idea. I've always been one to read things that are beneath my level because I might pick up some stray bit or previously missed fundamental. I don't feel that I've applied the concept so well to people.

To learn from the mistakes of people who just don't get it seems to me inefficient; that one may learn from the bad code and other artifacts they produce seems more efficient but still difficult. Can you expand? If one can effectively learn from the clueless there are vast territories in learning for me to explore.

I will put newly learned constructs into production code. This works for me; I suspect that I am more ponderously slow and careful than the average coder.

Idioms are idioms, they must be learned.

Checking your data, not assuming anything, and avoiding shortcuts are all points I agree with. I would merge those all together into a test test test statement. And one key to good testing is to build tests into the build system.

I agree entirely with your code bear comments. Also one may consider that many people do not listen as well as a inanimate object; I take that as a challenge to be a better listener.

Use every available resource is too simplistic. The wasted time I spent following the useless links in your node support my point. The quality of a resource is important. One can only deal with so many resources at a time. Hopefully, one absorbs resources and continues to find others to absorb.

Be well.
rir