This talk helped me articulate a few key arguments that I can use to counter myself when in the throes of impostor syndrome-related attacks from my inner monologue.

Basically, a “staff-plus engineer” is anyone in a technical role that is higher than a senior engineer. These are sometimes referred to as principal engineers, staff engineers, etc.

The big difference between staff-plus and individual contributor path is that an IC role is one you go down when you truly want to contribute as an individual, often acquiring such an expertise in a specific domain that you just do your thing alone.

A staff-plus role requires collaboration, often leading teams, but always being the lynchpin which helps be the voice of technical leadership across multiple teams.

The responsibilities of a staff-plus role include (probably) writing and (definitely) reviewing code, providing technical direction, mentoring and sponsoring other engineers, providing engineering context to non-technical people, and being involved in strategic projects which aren’t shiny but are critical to the success of an organization.

I think I came across this talk at a timely point in my career. I have been tasked with doing staff-plus engineering work ever since starting my first company, and it’s honestly the stuff I love the most.

I’m not a developer who loves to write code. I love writing code because it results in a tool that makes someone’s life easier. What brings me joy is in doing the discovery work needed to clearly articulate the problem and charting a course that’ll lead us to a solution.

I’ve known developers who’ve put up with the struggle with the expectation that one day it will go away: one day they’ll be an expert and never have to struggle again. This day never arrives, and so they bail out of the field.

Unfortunately, I don’t think the struggle ever goes away. I’ve been doing this professionally for 14 years now and I still have to deal with the struggle almost every work day.

If you can be comfortable with the struggle and build up your tolerance for it. If you’re able to sit in that moment and be okay without drama or a total crisis of confidence, I’m fairly sure you’re going to do just great.

The Struggle comes in multiple shapes and sizes too. Here is a short list of my experiences with The Struggle from this week alone:

• Impostor syndrome
• Anxiety about breaking a physical connector
• Frustration with unclear objectives
• Being overwhelmed by unfamiliar technologies
• Debugging something and being unable to find an answer

After 12 years of professionally dealing with The Struggle, I’m still able to handle many aspects of it, but my tolerance is quickly diminishing.

Dealing with The Struggle is much easier when you feel like there’s a reward for you at the end of it. Right now, I’m trying to restore my old iPod fifth gen with an SD card, and no matter what I do, I cannot get it to work right.

I’ve been all over forums, digging into the sixth and seventh pages of search results, desperately looking for clues as to why I’m not getting it to restore.

But I can picture myself playing that brick breaking game soon, and that first game is gonna be so much fun after all of this work.

When you embrace the idea that, yes, you were lucky, the fear drops away. And then you become more open to the possibility that the universe will continue to guard your back.

Because here is a truth that only a few discover: when you look for signs that the Universe is ‘friendly’ you will find them everywhere.

It is far better to live in a ‘friendly’ universe than an ‘indifferent’ or ‘hostile’ one.

I’m used to ascribing neutrality as the universe’s default mode, but I didn’t consider the possibility that a neutral universe can be harnessed in whichever way you want.

As a developer, whenever I see my code works right, I often squint at it in disbelief, wondering what I did wrong, feeling like it’ll break the second I push it to production.

Maybe in those moments where my impostor syndrome is peaking, I should accept the pat on the back from the universe and give it some flowers.

I saw this TikTok from Chelsea Fagan shared on a Slack community I'm part of, and I thought it was worth transcribing the whole thing and leaving it here for future reference.

So one thing about me is that I never have impostor syndrome, and it's not because I automatically think I'm great at anything I try... it's more that I realized that basically every industry is full of idiots.

I genuinely think that a lot of people who haven't been in the corporate world or exposed to it too much don't realize just how many successful people are mediocre at best at what they do.

And it makes sense when you consider all the factors that are usually required for people to reach a high level at a given industry. Things like having connections, having enough generational wealth to go to college and get an advanced degree, nepotism, networking, and all of those other things. Not to mention all of the other white, cis, male privileges that often go into success.

But by the time you reach the highest levels of most industries, you're often working with people who can barely put together an email.

Or you'll be on an email thread with 17 different people, none of whom seem to actually have a job.

Half of the executives have administrative assistants who do the vast majority of their actual work.

And this is true of a lot of creative industries... think of how many famous people are out there who have almost no discernible talent.

A driving force in my life is looking at something and being like "I could absolutely do better than that", and then I give myself permission to do it.

And just being the kind of person who is conscientious enough about the work you're doing to even consider having impostor syndrome, or think about whether or not you're good enough to be doing it, you're probably already better than most of the people there.

Related: this quote from Sarah Hagi:

Lord, grant me the confidence of a mediocre white man.