> Real tech people
Ah this fun gatekeeping meme rears it's head again.
So how do you define "tech" people? Do you have a scorecard?
How do they meet your assessment for "real"? Cohesive organization of atomic matter generally constitutes "real" in a lot of physics definitions.
I'd argue trying to label someone a "real tech person" is a laughably subjective exercise that's so corrupted by personal bias and toxicity as to be utterly useless in evaluating someone's capability to participate in organized software engineering.
Case in point: I have worked with several folks, in FAANG, who by all technical standards were "real" tech people. Polyglot programmers, could tackle any sticky logic problem.
Ask them to communicate their solution to other engineers? To communicate with others with empathy? Be able to navigate conversations with directors and VPs about broadly implementing their solutions? Absolutely, 100% fell on their face. Couldn't do it. They couldn't form a cohesive, understandable, actionable statement about their work to save their lives. They'd go off on some completely pointless technical tangent that had little to do with the problem at hand.
Code reviews they participated in ground to a complete fucking halt. Not because they actually addressed meaningful technical issues. No, they wanted to pontificate and show off how much smarter they were.
In my not totally hard-data experience, people that maybe didn't have quite the "real tech people" skills but were expressive, capable communicators often actually shipped more meaningful work, more often, and built organizational equity not just for themselves, but for their teammates and managers too.
Software development at any scale, like it or not, involves working with other people. In my experience people that go around gatekeeping and using some hilariously subjective ruler to grade "realness" aren't very effective at all.