I gave two stereotypes, yes, and anyone reading what I wrote should be aware that those are stereotypes and not always or exactly applicable, but I didn't write the original article and if anything I'm breaking up the more general stereotype they gave of "software developers are jerks", though into only two other stereotypes. I also meant to imply there is also a third class, which is developers who just aren't jerks at all. You can be a software developer and have social skills, I've worked with many of these people. Only about 35% of the people I've worked with were actually jerks.
To be clear, I don't think anyone should be a jerk, not even the people who are right when they are being jerks. But given the choice between someone who is going to be a jerk to me upfront in a meeting where I can rebut their arguments if I choose to do so, and someone who will nod and smile to my face and then talk shit behind my back to other coworkers and rally political forces against me, I'll take the first type of jerk any day, and those kinds of jerks are far more common than the other kind when it comes to actual software developers, in my experience.
> However it becomes bad when they refused to learn new (community accepted) ways of doing things that are either REQUIRED or lead to efficiency down the road.
I totally agree, which is why I'm 40 and I know JavaScript very well and I'm familiar with a lot of new frameworks using the language and write a fair amount of JavaScript despite the fact that I think it is a terrible language. And on the flip side of that, my absolute favorite language to code in today is Go, which is very "new" by programming language standards.
> I'm a young manager that has older coders and I defer to their wisdom 90% of the time.
Aren't we mostly agreeing then? I said that guy is "probably right", not "right". 90% is much higher than what I would normally consider "probably".
I gave two stereotypes, yes, and anyone reading what I wrote should be aware that those are stereotypes and not always or exactly applicable, but I didn't write the original article and if anything I'm breaking up the more general stereotype they gave of "software developers are jerks", though into only two other stereotypes. I also meant to imply there is also a third class, which is developers who just aren't jerks at all. You can be a software developer and have social skills, I've worked with many of these people. Only about 35% of the people I've worked with were actually jerks.
To be clear, I don't think anyone should be a jerk, not even the people who are right when they are being jerks. But given the choice between someone who is going to be a jerk to me upfront in a meeting where I can rebut their arguments if I choose to do so, and someone who will nod and smile to my face and then talk shit behind my back to other coworkers and rally political forces against me, I'll take the first type of jerk any day, and those kinds of jerks are far more common than the other kind when it comes to actual software developers, in my experience.
> However it becomes bad when they refused to learn new (community accepted) ways of doing things that are either REQUIRED or lead to efficiency down the road.
I totally agree, which is why I'm 40 and I know JavaScript very well and I'm familiar with a lot of new frameworks using the language and write a fair amount of JavaScript despite the fact that I think it is a terrible language. And on the flip side of that, my absolute favorite language to code in today is Go, which is very "new" by programming language standards.
> I'm a young manager that has older coders and I defer to their wisdom 90% of the time.
Aren't we mostly agreeing then? I said that guy is "probably right", not "right". 90% is much higher than what I would normally consider "probably".