Indeed, now there are so many tools that you can't just expect a reasonably experienced programmer to just know the tools that you're using. I can think of at

Indeed, now there are so many tools that you can't just expect a reasonably experienced programmer to just know the tools that you're using. I can think of at least two further difficulties that come with the explosion of available tools: 1. It’s hard to know whether a tool is actually worth using at all. Many tools sound appealing because you’re familiar with the problem they aim to solve but not yet familiar with all the quirks and edge cases and hidden costs of using the tool instead. 2. Many tools look promising in their early days, when they are prime examples of enthusiasm driven development. It’s another thing to ask whether the tool is still going to be in active development five years down the line, when there are newer and shinier things to work on. Even if there are, your 100,000 line code base might still need that security fix or one of the 10% of missing features that were on the roadmap when you first started integration. I’m all for using the right tool for each job, and I’m certainly in favour of using good tools rather than doing everything the hard way, but figuring out which tools those are gets harder as tools proliferate.