That is a separate point. The point I was saying was not relevant was "no matter how smart you are, youve got finite bandwidth and a finite time to spend it." This implies that people are not improving on things because of finite capacity to do so, which is sometimes true, but really just an edge case.
You're saying people don't need to care about X, which is true. However, if you choose to spend 10 hours building a pile of blocks, every day, rather than spending 10 minutes learning how to turn on the BLOCKMASTER 9000, you're just being obstinate. Hyperbole and arguments to your personal choice of block building aesthetic aside, there's a large class of problem for which the effort required to both improve one's capabilities and execute the task is much lower than the effort require to execute the task to begin. No matter how much you care about your kids, and how little you care about building blocks, if you must build that tower, it is beneficial to learn how to use the BLOCKMASTER 9000.
Pursuing the latest and greatest tooling mastery for incremental gains usually doesn't fall into this category. You don't need to pursue improvement endlessly. But say, people who refuse to learn how to use a debugger, but spend a great deal of time debugging? People who only share code over email while the team tells them to use git? People who only use global variables in painfully uncomfortable circumstances? If you're coming to work and refuse to invest in such things... it's fully plausible that you are a 0x or -1x programmer. Same for almost any other ___domain of work.
You don't need to care about anything. The reason you improve is because you want to be better. If you don't want to be better, and are currently bad, there's at least going to be a large social reason why you may want to change.
You're saying people don't need to care about X, which is true. However, if you choose to spend 10 hours building a pile of blocks, every day, rather than spending 10 minutes learning how to turn on the BLOCKMASTER 9000, you're just being obstinate. Hyperbole and arguments to your personal choice of block building aesthetic aside, there's a large class of problem for which the effort required to both improve one's capabilities and execute the task is much lower than the effort require to execute the task to begin. No matter how much you care about your kids, and how little you care about building blocks, if you must build that tower, it is beneficial to learn how to use the BLOCKMASTER 9000.
Pursuing the latest and greatest tooling mastery for incremental gains usually doesn't fall into this category. You don't need to pursue improvement endlessly. But say, people who refuse to learn how to use a debugger, but spend a great deal of time debugging? People who only share code over email while the team tells them to use git? People who only use global variables in painfully uncomfortable circumstances? If you're coming to work and refuse to invest in such things... it's fully plausible that you are a 0x or -1x programmer. Same for almost any other ___domain of work.
You don't need to care about anything. The reason you improve is because you want to be better. If you don't want to be better, and are currently bad, there's at least going to be a large social reason why you may want to change.