Nevertheless, in a way I still find myself subscribing to the idea that people in tech tend to fit these stereotypes. If I imagine a hypothetical group of [company name here] devs, I imagine them as all anime-watching gamer bros. On the other hand, when I actually encounter any particular developer, it would surprise me more to learn that they are an anime-watching gamer than it would to learn that they are not. I somehow picture groups of people to be members of a cultural group that I consider to be a minority.
I think this apparent contradiction might be caused by a discrepancy with how tech professionals are portrayed in media (as anime-watching gamer bros) with how they actually tend to appear when I meet them in person ('normal' yuppies, often young parents or 'DINKs', with a wide variety of hobbies and interests).
> evaluate programmers, it over-relies on heuristics and
> cultural traits that favor people who "fit the mold."
I think this is mostly wrong. It's hard to objectively evaluate many professions. How do you evaluate marketing professionals, or lawyers, or graphic designers? It's all fuzzy. And it's especially fuzzy for 22 years olds without a track record of experience to look at. I don't think that software companies do it much differently than anyone else when it comes to hiring. We base decisions on gateways like prestigious degrees. We look at whatever experience we can (even if it's just a github repo). And we conduct interviews where we do our best to ask real world questions.
Is this process perfect? Of course not. But is it pretty good? I think so. It's obvious who the great programmers are. It's obvious which ones are awful. And there's a mushy middle where it's hard to tell who's gonna work out and who isn't. I suspect that most other fields are about the same in this respect.
There's a lot more similarity at the level of experienced hiring obviously. And this model of hiring is expensive. But it also has benefits. Firms create new professionals from raw materials. They don't have to wait for trained professionals to walk in the door.
It's interesting to think about the first point though. Why are training practices different in software? I can think of a couple of hypotheses:
A) Programming is one of few fields where it's possible to self train. B) Programming is a relatively young field that hasn't matured enough to develop rigorous training practices. C) Software companies aren't profitable enough to support expensive training programs. D) Training of programmers is a relatively futile endeavor as most programming success will come from innate talent that is either present or not in any given individual.
Just off the top of my head I put the most weight on A and C (especially for startups) though I'm fairly uncertain. There might also be other reasons I haven't thought of.