From my direct, personal, experience, it goes something like this: "Don't you want better tools?" I'll ask "Of course!" the programmer replies (note sometimes

From my direct, personal, experience, it goes something like this: "Don't you want better tools?" I'll ask "Of course!" the programmer replies (note sometimes this is a conversation with myself) "but I don't want to pay anything for it" they caveat. "That's no problem," I reply, "as long as it will make your life better." "Well, that sounds good, but I also don't want to have to learn anything new." "That..." "Also, it has to just work from day one, if it doesn't quite work as soon as I touch it, I'll swear off it forever and go talk badly about it on twitter and hacker news." "Ah..." "Also, it has to work with every use case I can think of. Multi-threaded, GUI, deployed to HPC clusters running RHEL6 and also Docker containers running CoreOS, and it should be able to help me be productive in either JavaScript or s390 assembler. Also it should take no time to set up, and start giving me answers straightaway." "Hm..." "You know what, the methods I already have already satisfy all of these requirements and as a bonus, I don't have to learn anything new in order to use them. I spend enough time learning new frameworks to write software, why would I spend more time learning frameworks to debug software?" "Because you spend more time debugging software than writing software?" "Honestly the process of debugging, and the process of writing, have become so intertwined in my thinking, that distinction between them seems arbitrary and pointless." "Thanks for your time."