Yes! Many engineers use tools they like for reasons unrelated to the job they're doing or the product they're building.

It might still, at least arguably, be "the right tool for the job." If you have a huge team of expert C# developers C# might be "the right tool for the job" even if it would be a little easier to do in a different language, given the same pool of experts in that language.

Agree. My point is that, if I personally dislike C# (I don't), and I'm on a team of C# experts and C# is the best choice for shipping the product given those experts and all the other use cases, then C# is the best tool for the job and I'll peruse C# documentation. I try my best to focus objectively on the product, not my ego or subjective preferences...and I often fail :(.

I've been writing PHP for a couple months and I've been pleasantly surprised so I feel like I am moving beyond that.

To be fair, PHP 7.1 with Composer is a very different language to PHP 4, for the better of course.

Yeah, sure, and I was able to avoid the painful years. But C# pre-generics and pre-Linq is a way less appealing language too, you know? Most languages that are popular now look kind of rough to work in several versions ago.

Oh definitely. I think that’s the case for nearly any language that’s worth the code it’s written in. C++ is an interesting case study in how to do it both right and wrong; we’re spoilt for choice and it keeps getting better every day

At a place I worked at once, it was "use Microsoft for everything". So yeah.

Yeah but that's more a matter of the criteria to decide on the right tool. Nobody would say "I intend to use the wrong tool for the job."

> Nobody would say "I intend to use the wrong tool for the job."

...but there's plenty of sales charlatans out there who will say "I intend to get the manager of that IT dept to make its developers use my tool for the job, and I don't care if my tool is the right one or the wrong one."

> Does anyone believe in using the wrong tool for the job?

Yes. PHP developers.

:)