Very nice list. One thing that I find interesting is that I think some of the points can contradict a bit. This isn't unexpected for something of this nature, especially with as many bullet points as you include.

One thing that stands out to me is that I think that it makes sense to have a passion for certain "tools", including languages. Yes, we solve problems in what is needed for that task or that job, but that doesn't mean we don't try to pick the best tools for the job and have valid reasons why certain languages/frameworks are better than others. We should be cognizant of the shortcomings of all of our tools.

Personally, I prefer languages that help me to write high quality code quickly by having compilers that show me when I make simple mistakes. Everyone makes typos. Some languages/tools will point it out to you immediately so you can quickly fix it and move forward. Others don't. Other languages require that you run exactly the right test before that typo becomes a problem. In professional production environments, doing that run can take a while for a variety of reasons. Similarly, languages/frameworks differ in how well they give you feedback to fix those problems. The tools that give you a clear indication of what you did early in the process can be very helpful for maintaining flow and allowing a developer to keep moving.