The whole edifice of "social media", with it's collateral damage of depressed and suicidal kids, is just a great experiment for the likes of Mark Zuckerberg.
Nobody in nervous "academia" can get away with even the most gentle experiments now the ethical guardrails are in place (and mostly for good). But set up a "SV start-up" and you can do what you like with the data of billions, influence, propaganda, whatever...
Obviously, they always do: Arrogance requires ignorance in equal proportion: If you actually understand the complexity and uncertainty of reality, and then of your perception and thought about it, you can't be arrogant. The more arrogance, the more ignorance is needed. The cure for arrogance (and I know from personal experience!) is knowledge.
The ignorance of the humanities and social sciences leads to the absurdity of their megalomania, arrogance, and policies. I used to think they knew better, and could only guess why they did what they did. Then I realized I was overlooking the more simple, obvious solution that was staring me in the face, that is staring all of us in the face: They are just ignorant; they really don't know these things.
It's not true of all STEM, etc. but I had STEM-studying friends who brag that they never read a book. Many SV leaders and participants are from that crowd, apparently enough for it to be a powerful culture. They deride education, humanities, and social sciences, a parody of the ignorant that's been used in much of the literature (that they haven't read).
And more sad, is that people I know that do know better, people with even PhDs in humanities and social sciences, have followed the lead of the ignorant, rather than vice-versa. Rather than educating the world, they buy into the ignorance and worship of it.
The humanities and social sciences provide centuries of answers to the problems of today - not every answer, but we can certainly avoid this stupidity. We have everything we need, we just need to wake up to it.
> ignorance is something that can be fought with education and patient, sincere messaging.
Indeed. Hopelessness is our only obstacle, the only thing we have to fear is fear itself. I sincerely believe that.
I've taken my car into the mechanic before only to be told the problem isn't reproducible so then I eliminate variables to figure it out myself and essentially do their job for them. Once I enumerate exactly how to reproduce, it's all but clear what the problem is and then they can replace the part.
I'm positive it wasn't intentional, but you've done a fine job buttressing my argument.
So then the problem may be that average software developers overestimate their own ability ;)
Most of all, the actual professional - like any professional - has learned that it's unproductive to debate or educate the patient/customer; you just let them think they're smart and work around it. It's not your job to teach them the error of their ways, but to get your work done.
In IT, I've had plenty of clients tell me the most ludicrous nonsense. You just work around it; IT is your job, not theirs; don't humiliate them. Be respectful to people; they have hard days too.
I just tend to remember the times where they didn't do their job well. For example, my daughter had a rash, the doctor says to just put moisturizer on it. Doesn't seem to help so I research it for a few hours on google and conclude it's shingles. The doctor scoffs at my suggestion saying my daughter is way too young to have shingles and says to just continue with the moisturizer. We take her to a second doctor who confirms it's shingles.
So yes, I would admit my anecdotes are probably a form of survivorship bias and I'm letting a few incompetent doctors and mechanics taint the ability of their peers.
Some really good evidence that the answer is "false" is that developers who think it's true will use a handful of personal experiences to levy sweeping judgements about millions of people in a vast array of disciplines, many of which tackle some of the hardest problems humanity has ever undertaken in fields that dwarf the complexity of computer science immeasurably.
And I say this as an above average software developer (which sounds stupidly cocky to even say).
Honestly I could imagine a mechanic writing the opposite sentiment, saying they don’t respect software developers because they called a support line and the only advice was to restart the computer and then to reinstall it from scratch.
Coming from working class social/work/familial environments, I know this archetype well: John Ratzenberger's "Cliff Clavin" from Cheers. It's a dated reference, but it fits really well. The stereotype involves carrying large rings of keys on their belts, showing that they're entrusted with many valuable things, and frequently interjecting others conversations with things like "let me show you out to use that thing [blue smoke]" and "no no no you got it all wrong. What you gotta do is..."
In fact, I knew a particularly untalented auto mechanic who insisted that his capability was equivalent to a mechanical engineer when sadly, it wasn't even equivalent to most mechanics. None of us perfectly gauges our capabilities relative others, but some are so very much worse at it.
Not that it's specific to the software world, but definitely pervasive in it. Even as someone who spent half of their adult life as a developer, I'm frequently astonished by the false confidence many developers have about their understanding of unrelated disciplines. I can't tell you how many developers have tried to explain both design and cooking to me even when they know I'm an experienced and educated designer, and a classically trained former chef. It's not even like they're just trying to confidently wield the knowledge they have-- it's DK all the way.