DEV Community

Christopher Jakob
Christopher Jakob

Posted on

You feel like a fraud on your dev team. Let's fix that.

There is one habit that keeps that fraud feeling alive, and it is probably not the one you think. I will get to it, and to the small daily rep that weakens it.

Quick background so you know where this comes from. I'm Christopher. I spent nine years in the Marine Corps, then moved into software and data engineering, including edge computer vision work for the Air Force on a project called Athena. I have shipped code that ran on real sensors. And I have still sat in a standup convinced that everyone else on the call knew something I didn't, and that any day now someone would figure out I was faking it.

If that is you right now, you are not a fraud. Your filter is keeping score wrong.

Why the fraud feeling sticks around

I don't believe you build confidence. I believe you unhide it. The developer who walks a junior through a tricky bug without breaking a sweat is the same one who lies awake replaying a dumb question from a planning meeting. Your skill did not change between those two moments. What your brain chose to notice did.

Your brain runs a selective filter called the reticular activating system, the RAS. It decides what reaches your attention out of everything happening around you. It learns from what you feed it. If your early years in tech were full of brutal code reviews, senior devs who sighed at your questions, or a layoff that felt personal, your filter learned to hunt for proof that you don't belong.

And it is very good at its job. It flags the one PR comment that said "this is wrong" and skips the three that said "nice." It remembers the outage you caused and forgets the feature you shipped early. You are not seeing your record. You are seeing a highlight reel of your worst moments, cut by a filter that was trained on fear.

The habit that feeds it: hiding

Here is the habit I promised. It is not the self-talk. It is the hiding.

You don't ask the question in the meeting, so you never learn that the question was normal. You don't share the half-finished idea, so you never hear someone say "oh, that's good." You don't post the thing you built, so nobody gets the chance to say it helped. Every time you hide, your filter files it as evidence: speaking up was dangerous, and we survived because we stayed small.

Hiding feels like protection. It is actually training. And it is training the wrong thing.

You can't think your way out of this. Telling yourself "you're qualified, you passed the interview" bounces right off, because the filter does not run on arguments. It runs on experience. So you give it new experiences, small ones, on purpose, every day.

The daily rep: compliment a stranger

Once a day, give one genuine, specific compliment to a stranger. Great jacket. That's a cool bike. Your dog looks like it runs this neighborhood. Say it, smile, keep walking.

This sounds nowhere near a sprint retro, and that is the point. It is the same move at low stakes. You are putting your voice into a space where nobody asked for it, while your body braces for judgment. The first few will spike your heart rate. Then they won't. Your filter starts collecting a new kind of evidence: I spoke up, and it went fine.

That is rung one of a short ladder:

  1. Genuine compliments to strangers
  2. Light conversation after the compliment
  3. Longer conversation, still with no agenda

Move up a rung only when the current one stops spiking you. Rushing the ladder trains panic, not confidence.

Bring it to work

Once the stranger reps feel easy, start running the same reps on your team.

Ask one question per meeting. Not a clever one. A real one. "Can you say more about why we picked Postgres here?" Most of the room was wondering too.

Keep a receipts file. A plain text file. Every time you fix something, unblock someone, or get a thank you, add one line. Your filter only sees the misses. The file makes you look at the hits on purpose.

Share work before it's polished. Post the draft PR. Drop the rough diagram in the channel. Each time it does not end in disaster, the filter updates.

Compliment a teammate's work, specifically. "The way you split that migration into three steps made it easy to review." Giving credit out loud is the same muscle as taking it.

What Athena taught me about evidence

On Athena, edge sensors ran a local model. When the model flagged something significant, the system sent context from before, during, and after the event back to AWS so the models could keep learning. The models improved because they kept getting new, real examples.

Your filter works the same way. Right now it is training on a stale dataset full of your worst days. Every rep you run, every question you ask, every line in your receipts file is a fresh example. Feed it enough of them and the fraud feeling loses its grip, because it no longer matches the data.

You already have the skill. You already have the voice. Old training just taught you to hide them.

Your mission this week

  • Compliment one stranger a day for seven days.
  • Start a receipts file today and add one line every workday.
  • Ask one real question in at least three meetings.
  • On Friday, read the file out loud to yourself.

Then tell me in the comments: what is one thing you shipped this year that your brain keeps trying to forget?

Top comments (1)

Collapse
 
ace_bl profile image
Ace •

This one hit home. The idea that you don't build confidence, you unhide it, is going to stick with me for a while. Hearing that someone with nine years in the Marines and real shipped sensor code still feels that standup dread makes it so much easier for anyone reading to believe they're not the only one. Thank you for writing it so plainly. What was the first small win you noticed once you started retraining that filter?