Yes I too have ‘Imposter Syndrome’


The Ted that graduated from Coding Dojo and got a super well paying job so quickly after graduating bootcamp??

The one who’s face is all over Coding Dojo’s marketing emails and website??

Me and my cheesing face.

I’m seen by many as this shining beacon.

The type of person that all aspiring developers aim to be like.

But in the grand scheme of things, I’m just another developer sitting at his desk, figuring out a coding problem.

I’m surrounded by extremely brilliant folks all around me that are smarter than me and are much more accomplished than I am.

As I’m going through the 100 Days of Swift and blogging my way through I can’t help but to think to myself:

I’ve been developing for over 2 years now.
Why am I still struggling through a beginner coding course? 
I should be so much farther ahead.
Why did it take so long for me to start learning Swift development?
What have I been doing this whole time?
Why is every other developer so good at coding?
Why am I so slow to pick up new things?

I spent that night with a bottle of tequila.

Tequila only responded with: “Dude just fucking relaaaaaax”.

It was only this morning that I felt better when I found an article written by David Walsh.

This guy here is a developer much more accomplished than I am.

Despite all his success still can’t shake off the feeling that he’s an “imposter”.

He lists out many reasons why developers are always susceptible to “imposter syndrome”.

Our competition isn’t the next local guy — web development is a profession where our colleagues and competition are anyone with a computer and internet connection, all around the world
Every programming task’s efficiency is measurable, meaning our colleague can write a routine to complete the same task and it may be 1300% more efficient, making us feel that much worse
APIs change so often that we need to keep a keen eye or fall behind
We’re in that “in between stage” where we (1) know how we’ve bastardized APIs in the past and (2) are trying to perfect new ones, so we need to feature test for everything
We forget we’re pushing the limits of the web, its APIs, its browsers, and its devices
Promises and async are just hard
Users can be very dumb but it’s still the developer’s fault for not making something easy enough
We forget that our job is just a fraction of our lives and there’s a real world outside of this hateful, illuminated screen
We probably stay on our computers after the “day job” which leads to intense feelings of being burnt out

It’s a tough industry. And I’m taking David’s advice on what I can do to make myself feel less like an imposter.

Look at your (hopefully decent) employment history and know that, on a basic level, you’re much more wanted than you’re wanted gone
Log onto the IRC channel of a skill you feel comfortable with and answer questions of those asking
Realize that people who consider themselves “experts”, and don’t go through waves of self doubt, are idiots that are so arrogant to not know what they don’t know
Remember the last time a non-developer friend asked you the most basic of computer-related questions
Perform any simple exercise in the JavaScript console
BLOG! The worst thing that can happen is someone corrects you and you learn something out of it
Review your code and find little nits to fix

I took his advice and went over to and began answering whatever questions I could.

I still couldn’t believe I didn’t have ANY reputation points.

But after a couple hours, I submitted two “accepted answers” and some “upvotes” and got 50 points!

I’m probably not ever going to get rid of this “imposter syndrome”

and I think that’s okay.

As long as I don’t have too many nights with just me and tequila. :D


Like what you read? Give Ted Y Whang a round of applause.

From a quick cheer to a standing ovation, clap to show how much you enjoyed this story.