Having worked in technology in the Midwest, the Pacific Northwest, and SV as well as working regularly with (and at) teams on the East coast, in the south, Japan, Taiwan, China, India, Europe, the UK (it ain't Europe now!), I've found this tendency of those in technology, and especially software, to discount the complexity and systematization of other fields, disproportionately common.
I was well and truly familiar with the classic "why don't you just..." way of speaking before I'd ever even visited the bay. Similarly, I'd witnessed (and participated in) mocking of domain-specific jargon when I was younger, and I see it still today.
It's not data, but my experience in the space strongly supports the suggestion that a dismissive, reductive, and aloof posture is quite common in tech. It's one reason that I regularly tell team members that engineers should be professional pessimists, especially about themselves and their ignorance.
(Kidding)
Having worked in technology in the Midwest, the Pacific Northwest, and SV as well as working regularly with (and at) teams on the East coast, in the south, Japan, Taiwan, China, India, Europe, the UK (it ain't Europe now!), I've found this tendency of those in technology, and especially software, to discount the complexity and systematization of other fields, disproportionately common.
I was well and truly familiar with the classic "why don't you just..." way of speaking before I'd ever even visited the bay. Similarly, I'd witnessed (and participated in) mocking of domain-specific jargon when I was younger, and I see it still today.
It's not data, but my experience in the space strongly supports the suggestion that a dismissive, reductive, and aloof posture is quite common in tech. It's one reason that I regularly tell team members that engineers should be professional pessimists, especially about themselves and their ignorance.