Maybe this is me being in a bubble or something, but I've never heard a developer (in school or at work) claim to have Aspergers. I've encountered many software developers who have experienced Imposter Syndrome.

It came weirdly into vogue around 2013-2014 I think? It wasn't a massive thing but I do remember it coming up far, far more often than it has before or after.

I agree wholeheartedly with your points.

Responsible, experienced engineers should teach newcomers that experiencing self-doubt is part of the process in maturing. I had the fortune to work under a mentor in my original position in this company that wasn't afraid to pull his assigns in to help solve problems he was working on.

Seeing that people of his caliber still acknowledge the value of second opinions and eyes really helped me understand that this business is not about the individual bodies entombed in cube walls, but a complex effort of many teammates.

After I embraced that, I learned where I could, and contributed where I could, and I personally feel much more productive as a member of my new team because of that. Do I still feel like I don't know things? Definitely. I also know that it's a big field and we all won't know everything.

My next goal is to find my way to a leadership position so I can perpetuate this kind of mentality downwards.

Eh, I think "imposter syndrome" is a natural consequence of moving into a more selective environment and resetting your baseline estimate of your competence.

If we pretend for a moment that hiring processes are perfect methods for identifying the top X% of candidates objectively, when you are hired by a company that only hires the top 10% of candidates, when you are hired, you instantly go from being better than 90% of your cohort to being average. You might go from being in the 92nd percentile of your old cohort to the 20th percentile of your new cohort.

Sure, it's less stark when hiring processes aren't perfect and hiring criteria are fuzzy and don't oerfectly match the actual job requirements, but any time you go through a selective process it's going to happen a little.

to me it seems more of an issue with the environment than the individual. if everyone on a regular basis admitted that the answer to a particular problem isn't coming to them right away - we could avoid the wasted months where a new developer or one thats simply new to this organization spends their life flinching in fear of reprisal.