Friday, October 04, 2019

How Things Work

I use a lot of software, mostly for work although also for entertainment purposes. But I'm not a particular fan of software. I'm especially not a fan of the tendency towards "the new hotness" - the tendency for some fields to see a constant ongoing churn of new tools doing almost exactly the same as the old, but that people jump onto en masse because it's new.

My preference, frankly, is to use a much smaller set of tools, but to use them well. That in turn requires stability in the toolset - ideally, you should choose one tool for each job, and then stick with it until and unless something comes along that demands that you change.

(That "something" is of course subjective. You might find that a tool that was previously free starts charging and so requires a change. Or maybe the tool simply stops being supported. Or perhaps the new tool has some killer feature that means it's vastly superior to the old, to the extent that the change is warranted. But simply being newer is, for me, not sufficient, and neither is simply being presented with a marketing brief that has a few more check-boxes filled out. New features are only worth anything if you're actually going to use them, and if you're constantly switching from one tool to the next, you're never going to make good use of anything but the basic features.)

Funnily enough, two examples of the benefit of this approach have cropped up quite recently. Yesterday there was some discussion of how to use a particular feature of Excel, which is a tool that I'm definitely not expert in using, but it's also a tool that I've used basically forever and expect to continue using forever. So there was value in digging through various guides and tutorials to find the answer, and thus expanding the set of things I can now do with Excel. If we were in the habit of replacing our spreadsheet program every six months, it would not have made sense to do that. (And, equally, it's likely that the knowledge of how to do it wouldn't have been so easily available.)

The second concerns one of the uses of our build tool. This one is new (to us), but it's also a tool we'll be using very heavily, and it's also a tool we'll continue to use for the lifetime of the product (probably five years or more). So, again, it make sense to keep learning the intricacies of the tool with a view to getting really good with it.

No comments: