I feel like the analogy has always been about spending time now so that I save time and reduce errors in the future. Often to me it isn't replacing tools so muc

I feel like the analogy has always been about spending time now so that I save time and reduce errors in the future. Often to me it isn't replacing tools so much as spending time figuring out how to use them more efficiently. I don't feel like "switching" tools is the right way to think about this. It MIGHT be the right choice, but usually it is about learning how to use your tools well and leverage the capabilities that require preperation or familurization. Examples are: 1. Creating templates inside your tools. Like any jetbrains ide. This has literally saved me years of time in laguages that have more boilerplate like java. 2. Configuring your tools to your usage patterns, using plug-ins or extensions. Once done, I could do something like generate my style of code in keystrokes. If I found myself making something more than once that isn't reasonably abstractable, I often made templates, plug-ins or infra. This can also be extended to something like if I know I am going to be configuring some type of system a bunch and I anticipate the technical/business needs changing a bunch, I'll spend the time to create a fluent configuration interface for it and it saves me TONS of time in the future.