I’m working with a 10x engineer who’s most likely autistic and produces more than everyone else. He’s taking the team down because he steals work from others and nobody can learn the codebase. It’s also really bad code so he’s the only one that can understand it and refuses to document or explain what is going on. Is it rare or is it a common situation?
The title is not a question, but a statement. There are no evidence more than this anecdote to support this statement, and it's a very harsh one, putting all autistic people in one basket - despite the likely chance this has more to do with the person than autism.<p>Please be more careful when putting out/framing your personal thoughts than this. It's the same category as racism.
As the commenters have pointed out, you're creating lots of negative reactions by asking your question in this way. I'd add that you don't need the word 'autistic' here at all - your question would be clearer without it. Also, your text implies ("most likely") that you don't actually know if he's autistic, or why that would be relevant. You'd be better off sticking to what you do know—i.e. reporting your own experience and direct observations. Then you'll be able to give people more information.<p>Actually, your title would be better off without "thinks they're better than everyone", too, since (unless you have a mind reader) that's not a direct observation either. If you describe your situation more factually and neutrally, you might get a better response from the community. Just a thought.
I think if you remove the word “autistic” from the title then almost everyone on HN would have worked with someone like your description.<p>I’ve worked with a few. They’re usually solid over-achievers in general, and have gotten by with their toxic personalities due to their above-average output. They’re a burden on those around them but management just see the output so don’t really care.<p>I’ve quit jobs due to people like this.
This is weird, because i know two good engineers on the autistic spectrum (one visibly Asperger, who literally can't lie and have difficulties with irony, the other a bit more subtle) and they are really detail-oriented and love to document everything because this is good practice and also a ritual.<p>I don't know what "bad code" is (undocumented?), one of them really like his tricks (especially obscure ones), but each time document what the line does. Also, and i think this has to be because we were taught that at the school, they really like small functions (more than 20 lines of code and they start sweating) and modular code, so i guess to me it is really good code (i was at the same school)
I would say this particular situation is rare but the underlying problem is pretty common.<p>This is a management problem manifesting as an IC problem. If management is aware of this jerky behavior and lets it continue, they're hobbling the team and limiting their overall productivity. If they're unaware of the problem, they're just clueless.<p>Either way, you probably want dip out on that team. If you're the conscientious sort, you can tell them why as you go.<p>Also:<p>> 10x engineer<p>> he steals work from others<p>> It’s also really bad code so he’s the only one that can understand it and refuses to document or explain what is going on<p>10x more code produced != 10x better engineer. When people talk about "10x engineers" they usually mean the latter.
Yeah we have the same coworker. He diminishes other people’s result and make it impossible to scale the team by taking over work than others could do and learn from. When he’s expressing his opinion that nobody seems to be able to do the work, it’s pretty much that he’s not willing to train the other engineers to do the work. What does the company do? They either listen to him, fire people, and waste indefinite time trying to hire someone who can match the 10x engineer’s skills, or they try to remove the 10x engineer as the bottleneck that prevents the team from growing (also, if they don’t act fast enough everybody has left except the 10x engineer)
I don't know about autistic IANAD - but I've met the behaviour in several companies. Often the code was bad and not complete, used new technology to tackle a problem, then person moved on to new code/technoligies when they get bored, leaving ruins. Had always the highest standing with management because he was an "achiever".
Your coworker may or may not be autistic but the behaviors you describe are fully unrelated to autism. Perhaps a better term, according to your descriptions, is narcissistic. You cannot reason with an extreme narcissist in a meaningful way because the intent is always self serving at expense to everyone else.
You're not working with a 10x engineer. It sounds like you're working with someone who may think they're a 10x engineer, but they're likely just reducing the effectiveness of the rest of the team. Hopefully your company/team's management is aware of the distinction. If not, you and the team need to communicate this to them (in a tactful manner).<p>I've worked with people who were truly 10x engineers and others who just thought they were 10x engineers. The actual ones did this by succeeding in the context of the broader team. The ones deluding themselves just made everyone else miserable, and then left messes to clean up when they left.
I think this is very shortsighted, but also not unexpected. As far as I understand, someone who is autistic often does not consider themselves to be autistic. But also autism is a problem of social cues. Maybe this person is in capable of self regulation and monitoring, and so he thinks he’s great, it’s everyone else who is bad. That’s just a classic defense mechanism.<p>Bottom line, working with someone who is autistic can be extremely difficult, but it’s not their fault, it’s mostly their defense mechanisms in response to the way people are treating them.
You mean autistic employee, singular.<p>Whether the behaviour "comes from" his autism or not should not have any bearing on how you deal with it. (This is not legal advice)<p>Do you not have a code review step to prevent bad code from entering the repository?
I suspect writing bad code with poor documentation has nothing to do with autism. I'd suggest don't treat him different than any other employee.<p>If he steals work he steals work, less to be done by you. If he crashes and burns, so be it.