Could you expand on this? I would be interested in what part you find 'rare' -- I find there are tons of different niches/archetypes that a SWE can have.
Could you expand on this? I would be interested in what part you find 'rare' -- I find there are tons of different niches/archetypes that a SWE can have.
- Attention to detail
- High frustration barrier
Over the course of a career those become less and less important as one learns to use the appropriate tools (e.g. linters) and processes, but you still need them to get to that point. Especially for beginners, those two in practice most often break the "everyone can learn to program" trope, that I'd like to be true.
Indeed. Everyone can learn to write code. Not everyone can learn to program.
http://www.eis.mdx.ac.uk/research/PhDArea/saeed/SD_PPIG_2009...
The person who for some reason is up on a Saturday night reading the NGINX source code in C to better implement their company's Lets Encrypt integration.
The person who actually stepped through Kelsey Hightower's Kubernetes the Hard way just because they thought Kubernetes was really cool.
The person who writes code for personal projects during "social hours" where others may be out with friends, out with their significant others, etc.
EDIT: I'll leave it for the integrity/honesty of the comment, but here are some descriptors I wish I'd used in the first place instead of 'autism':
* On the spectrum
* Extreme Introvert
* Socially disconnected
* Ties self-value to work-output in extreme ways
* Seeks joy from work versus social interaction & status
(1) Classical autism
(2) Autism spectrum disorder (ASD)
(3) Broader autism phenotype (BAP)
If people were to understand you as talking about (3), well I don't think you said anything inaccurate. You obviously weren't talking about most individuals included under (1). As far as (2) goes, well at one end (2) includes (1), and at the other end (2) has a very vague boundary with (3).
Everyone seems to be missing this. It doesn't have to be in the DSM criteria, the parent poster is talking about the popular view.
I don't necessarily agree – I don't seek joy from work but I do things that others (my wife included) would consider as "work". The moment you tackle that label on them – or whenever I lose control of what I'm supposed to be doing – I'll no longer have the same joy.
> The person who for some reason is up on a Saturday night reading the NGINX source code in C
Sigh
Now this I have issue with. I think the best programmers I know will do something like this out of their own self interest. Maybe they are setting up some elaborate and over-engineered system for their own amusement.
If this is for work, though? You bet your ass I'll be reading that NGINX source code, if I have to, during work hours, however loosely defined those are. There are exceptions, of course. Sometimes your mind will be so focused on something that it _just won't let go_. In which case, fine, Monday can't wait and I'll try this thing. As long as there is no expectations from the part of the company.
Saturday night I'll be mucking around with 3d printing, game engines, programming my own blog software for the 30th time in a new Scheme dialect, anything. Just not work.
I wouldn't identify any of your examples as signs for someone being on the autistic spectrum.
(And the boundary between BAP and ASD is rather ill-defined and subjective anyway.)