My favorite way to prevent this is by working backwards. Use what other people already know. Not only does that mean I'm using trusted and tested stuff, it pre

My favorite way to prevent this is by working backwards. Use what other people already know. Not only does that mean I'm using trusted and tested stuff, it prevents the issue where even good documentation is useless if everyone else ignores it. If I do something new, other people ignore it till there's a problem and I'm not available, and they have to learn it last minute. If I use stuff they already know, they are already deeply familiar with it and will be able to solve problems as they occur. Everyone always talks about the core skill of programming as breaking down a problem into pieces and implementing them in the best way. I think of it as figuring out how to make a problem fit what's available, and being able to assess when it's worth trying to do something new, and when it's best to use what you have even if it doesn't fit at all.