I consider a tool that requires me to dig too much inside its internals a bad tool, and a tool I can't start using, even if in a very inefficient way, after rea

I consider a tool that requires me to dig too much inside its internals a bad tool, and a tool I can't start using, even if in a very inefficient way, after reading 2 minutes of quick start, a tool that is not good for me. The problem is that learning to build/configure/use XYZ is almost always a wasted effort, it is not like learning a new algorithm that will be useful knowledge for decades, so if the effort is too big I consider it wasted time. Examples of tools that are not easy to master but that I'm trying to learn well are vim (it's 15 years I use it), and git. Both tools pay back a lot, and in the case of git it is hard to learn not because it is hard per-se, but since you are learning general concepts about distributed VCS, so it's not a wasted effort.