| I really enjoyed how the post was laid out —- the structure caught and kept my attention and made the arguments easy to follow. Unfortunately, I’m not convinced. The author makes a good case for experimentation, but not for “tool maximization.” I think there is a case to me made for “find tools that do your work for you” —- that’s “buy, don’t build” —- but that case was not made here. Further, I think that it’s easy to actually overwhelm yourself with too many tools, at which point you’ve exhausted your interest and willingness to learn them. I have several “code time” extensions, which I installed under this exact line of thinking. I still haven’t made the evaluation of which one I prefer. I picked one by default and kept the others “just in case.” And I have plenty of other extensions that I plan to someday evaluate. I think the best tool use and evaluation comes from a sense of immediate necessity, just like the best learning comes through immediate practice and application. Everything else is just imagination, which can be hard to sustain and substantiate. |
Thank you.
> Further, I think that it's easy to actually overwhelm yourself with too many tools, at which point you've exhausted your interest and willingness to learn them.
I think most of the counterarguments in the comments to this post will have a similar idea to this. My thought is that this phenomenon occurs because of a lack of tool intelligence in handling tools. What those comments show is that more content is needed on how to survive among numerous tools and how to easily filter tools. Some things are hard to use alone without something else, and this seems to be the case.
> I think the best tool use and evaluation comes from a sense of immediate necessity
You assume that people can know what tools they need. Considering my observations, that doesn't match reality. That doesn't mean a dancer has to go through all the Excel documents they don't even use, but it's easy to narrow down the candidates for what might be relevant to you.