That is, unless you're good at it, or you're popular and software engineers are rarely either ... and never both.

The kind of people I usually meet are opinionated or mercenary and have that "not invented here" attitude - Or even an "if you invented it then it can't be any good" vibe. Sometimes they're one of those "What you should do" types - who are keen to offer advice that only works in their world; they would never do anything as radical as do something about it and if they did it wouldn't be appropriate anyway. Or at the very best ... "I work this way, I know what I likes and likes what I know" ... and very very occasionally "I'm too old to change", which is a very passive aggressive kind of excuse saying - really I can't be bothered with this. The worst kind must be those who offer (out of politeness or temporary enthusiasm) and then don't actually do anything and leave you in the lurch.

But in general it's the old "opinions are like arseholes" thing ... Everybody has one but never wants to even sniff at anybody else's.

Well, I've been software engineering in 'C' for a fair few years. It's very old fashioned nowadays. But I still program in C (using vi/gvim mainly) and I can often out code (not in terms of speed, but quality) many practitioners because I've bundled the "algorithmic patterns" experience of all my closest engineer friends and designed a method similar yet unlike the most common but inappropriate tools to help me write bullet proof code in a short a time as possible.

I can and do program in other languages ... but none are as fast when designing big systems and few produce code that is so robust.

I present snippets of it on this site. You can either benefit from it ... or ignore it.

It's up to you!

Archibald