A tool is worth using if it makes the work clearer, faster, or easier to communicate. It’s not worth using because it’s new, popular, or what your team uses. The right tool is the simplest one that does the job. Tool collecting, switching to something new before you’ve exhausted the current one, is procrastination dressed as process improvement. The time spent learning new tools is time not spent building with the ones you already know.
[[Software design should be opinionated]] applies here too: a team that commits to tools and uses them consistently ships more than one that keeps evaluating alternatives. [[Do less]] is the same discipline applied to tooling: pick one, use it until it fails you, then reconsider.