This is my perspective as well. Be able to apply, or write an appropriate tool for a job, and recognize a given tool's suitability for a task. This means, you d

This is my perspective as well. Be able to apply, or write an appropriate tool for a job, and recognize a given tool's suitability for a task. This means, you don't identify yourself as a "python programmer", "react programmer" etc, but are able to evaluate a range of tools. And, understand how the tools work, and know how to build one. This likely will involve some low-level (think register-level) code. Or for web stuff, being comfortable with network architecture and web standards. Another way of phrasing it: Being a general, cross-domain programmer, vice a provincial one. Being able to recognize when a best-practice or dogma in a given domain isn't applicable, because you are familiar with multiple sets of these practices, and therefor recognize their mutual inconsistency.