DEV Community: Christopher Jakob

Why You Go Quiet the Moment Someone Asks About You

Christopher Jakob — Wed, 04 Nov 2026 23:10:20 +0000

You are good at keeping a conversation going. You ask questions. You listen. People tell you about their jobs, their kids, their weekend.

Then they turn it around. "So what do you do?" "What about you, any plans this weekend?"

And you give a one line answer, shrug, and flip it right back to them as fast as you can.

Later you wonder why the conversation never really went anywhere.

Your brain treats attention like a threat

There is a part of your brain called the reticular activating system, the RAS. It filters what you notice out of everything going on around you. If enough past moments of being the center of attention went badly, it learned a rule: attention on you means danger.

So the moment the spotlight swings your way, the filter starts scanning. Are they bored? Did that sound weird? Am I talking too long? Your mind is so busy watching for judgment that there is no room left to actually answer the question.

Asking questions feels safe because the attention stays on them. That is why you are great at it.

Why preparing better answers does not fix it

A lot of people try to solve this by rehearsing. They come up with a smooth answer to "what do you do" and a couple of stories ready to go.

It helps a little. But the filter does not care how polished your answer is. It cares whether being looked at has been safe before. You cannot script your way past something your brain learned through experience. You have to give it new experiences.

Retrain the filter in small steps

Start smaller than you think you need to.

Give one genuine compliment. "Great question." "I like that jacket." Short, kind, done. You are teaching your brain that a few seconds of attention on you went fine.
Add one true detail about yourself. When someone asks about your weekend, give one real detail before you ask back. "I tried a new taco place, it was great. What about you?" One sentence about you, then hand it back.
Let it run longer. When step two feels easy, add a second sentence. Then a short story. Let the attention sit on you a little longer each time.

Move up only when your current step feels boring. Boring is the sign your brain stopped treating attention as a threat.

Count the rep, not the reaction

After the conversation, skip the replay of whether they seemed interested. Ask one question: did I share one true thing? If yes, you won. That is the only scoreboard that changes the filter.

I used to be the guy who once spent four hours walking around Chicago trying to work up the nerve to talk to one stranger. What changed it was not a better script. It was small reps, every day, in the right order.

I put the whole method into a short field guide called The Confidence Download. It has the three step ladder, the one question scoreboard, and a 90 day tracker so you can watch your reps add up. If you want it, it is here: https://payhip.com/b/oxt6n

Next time someone asks "what about you," give them one true sentence before you hand it back, and count that as a win.

Why It Feels Like Everyone Is Watching You When You Walk Into a Room

Christopher Jakob — Tue, 03 Nov 2026 23:08:34 +0000

You open the door to a party, a meeting, a new class. Conversations are already going. And it feels like every head in the room turns toward you.

Your walk suddenly feels strange. You do not know what to do with your hands. You head straight for the snack table or your phone, anything that gives you something to look at.

Then later someone says, "Oh, I did not even see you come in."

So which one was true?

Your brain is running a spotlight on you

There is a part of your brain called the reticular activating system, the RAS. It decides what you notice out of everything happening around you. If you have had enough uncomfortable moments in rooms full of people, it learned to scan for one thing: signs that you are being judged.

When your brain is searching for judgment, it finds it everywhere. A glance in your direction becomes a stare. Someone laughing across the room becomes someone laughing at you. A person who looked away becomes a person who decided they do not like you.

The room did not change. Your filter did.

Why telling yourself "nobody cares" does not work

You have probably heard that nobody is paying attention to you, that everyone is too busy worrying about themselves. It is mostly true. It also does almost nothing when you are standing in the doorway with your heart pounding.

That is because the filter was not built by logic. It was built by experiences. You cannot argue it out of what it learned. You have to give it new experiences that prove something different.

Retrain the filter in small steps

Start so small that your brain barely registers a threat.

Give one genuine compliment to one person. "I like your shoes." "This place is great." Then you are free to go. You are not starting a conversation. You are showing your brain that a stranger in a room can be a good moment.
Add one light line after the compliment. "Have you been here before?" Let it go wherever it goes. Ten seconds still counts.
Stay for a longer conversation. When the first two steps feel almost boring, let a conversation run for a few minutes.

Move up only when your current step feels boring. Boring means your brain stopped treating the room like a stage.

Count reps, not reactions

When you walk out of a room, skip the replay of how people looked at you. Ask one question instead: did I do the rep? If you gave the compliment, you won, no matter how they responded. That is the only scoreboard that retrains the filter.

I used to be the guy who spent four hours walking around Chicago trying to get up the nerve to talk to one stranger. What changed it was not a pep talk. It was small reps, every day, in the right order.

Next time you walk into a room and feel the spotlight, find one person, say one kind thing, and notice how fast the spotlight fades.

You take the first job offer because you're scared to negotiate. Let's fix that.

Christopher Jakob — Tue, 03 Nov 2026 18:37:29 +0000

You get the offer, you feel relief, and you say "yes, that works" before they finish reading the number. Then you spend the next year wondering what you left on the table. I will show you why your brain does that and the small daily rep that gets you to say "can we talk about the base?" instead.

If you always take the first offer, you are not greedy for wanting more and you are not ungrateful. You are protecting yourself from a few seconds of awkward silence, and paying for it every single paycheck.

What you actually hear

The recruiter says: "We're excited to offer you the role at this number."

What you hear: "Don't push it. They could change their mind. You barely got this. Say thank you and sign before they notice."

So you say "that sounds great." The call ends, the adrenaline fades, and you start doing the math on what you might have asked for. Or worse, a few months in you find out the person next to you, doing the same work, asked once and got more.

Here is the part that took me years to see: the offer was an opening. Companies expect a conversation. You treated a first draft like a final answer.

Why it hits so hard

I don't believe you build confidence. I believe you unhide it. You already know your skills are worth something. You just spent weeks proving it through interviews. What is missing is not value. It is permission to ask for something and let the other person decide.

Your brain runs a selective filter called the reticular activating system, the RAS. It decides what gets your attention, and it learns from what life fed it. Maybe you grew up hearing that talking about money is rude. Maybe you asked for something once and got laughed at. Your filter took notes: asking for more equals rejection.

So now, on the offer call, the filter skips past the fact that they already chose you and locks onto the risk of losing it. You cannot logic your way out of that. "Just negotiate" bounces off, because the filter does not run on logic. It runs on experience. So you feed it new experiences.

The daily rep: compliment a stranger

Once a day, give one genuine, specific compliment to a stranger. Nice jacket. Great laugh. That dog is a legend. Say it, smile, keep walking.

I know that sounds unrelated to salary. It is the same muscle at low stakes. You are saying something out loud, to someone whose reaction you can't control, while your body braces for it to go badly. The first few will spike your heart rate. Then they stop.

The rule that makes it work: the win is the action, never the result. They ignore you, win. They light up, win. You only managed to think it, still a win. If you only count the ones that go well, you are training the old program that says asking only counts when people say yes. The rep is the point.

That is rung one of a short ladder:

Genuine compliments to strangers
Compliment plus a quick "how's your day going?"
Small asks in daily life: a better table, a different size, "is there any flexibility on that?"

Move up only when the current rung stops spiking you.

Bring it to your offer

Once the stranger reps feel easy, run the same reps on the offer.

Buy yourself time. You never have to answer on the call. "Thank you, I'm really excited about this. Can I have a couple of days to review the full package?" is a complete sentence.

Ask one clear question. You do not need a speech. "Is there flexibility on the base salary?" Then stop talking. The silence after an ask feels like an hour. It is usually about three seconds. Let it sit.

Anchor on the work, not your bills. "Based on the scope we discussed and what I'm seeing for this level, I was hoping for something closer to X." That keeps it about the role, which is what they are paying for.

Have a second ask ready. If base is locked, ask about a signing bonus, extra PTO, a title, or a review in six months. One no does not end the conversation.

Count the ask, not the answer. Same rule as the compliments. You asked, win. They said no, still a win. You found out where the edge is, and you trained your filter that asking did not kill you.

What Athena taught me about asking for more

On Athena, edge sensors ran a local model, and when it flagged something significant it sent context from before, during, and after the event back to AWS so the models could be retrained. The system got better because it kept asking for more data instead of assuming the first pass was good enough.

Your first offer is the first pass. It is not a verdict on your worth. It is a starting point both sides expect to adjust. Treating it as final is like shipping a model after one training run because you were afraid to look at the results.

You already earned the offer. Old training just taught you that asking is the dangerous part.

Your mission this week

Compliment one stranger a day for seven days.
Make one small ask in daily life where the answer might be no.
Write down your offer script now, before you need it: the thank you, the time ask, and one question.
If you have an offer on the table, ask one question about it. Then let the silence sit.

Then tell me in the comments: what is the one thing you wish you had asked for in your last offer?

Why Your Mind Goes Blank the Moment a Stranger Talks to You

Christopher Jakob — Mon, 02 Nov 2026 15:15:17 +0000

Someone at the coffee line turns and asks how your day is going. A new coworker says hi in the kitchen. A friend of a friend sits down next to you at a party.

And your mind goes completely white.

You know words. You use them all day. But right then, nothing comes. You say "good, you?" and the conversation dies, and you spend the next hour thinking of all the things you could have said.

Later, alone, you are funny and quick. So what happened?

A blank mind is a stress response, not a personality trait

There is a part of your brain called the reticular activating system, the RAS. It filters what you notice and decides what matters right now. After enough awkward moments with people you did not know, it learned to treat a stranger's attention as a threat.

When your brain senses a threat, it narrows. Attention goes to scanning for danger: how you look, whether they are judging you, how to get out. The part of you that pulls up stories, questions, and jokes gets pushed to the back of the line.

So the blankness is not proof you have nothing to say. It is proof your brain thinks this moment is dangerous. Those are very different problems.

Why trying harder to think of something makes it worse

The usual advice is to have topics ready. Memorize three questions. Keep a story in your back pocket.

The trouble is that a brain in threat mode cannot reach for the back pocket. Now you are standing there blank and also failing to remember your list, which feels even worse. The RAS logs it as one more reason strangers are dangerous.

You do not fix a fire alarm by shouting over it. You fix it by showing it, again and again, that there is no fire.

Teach your brain that strangers are safe, in small steps

The filter got trained by experiences, so it gets retrained by experiences. The key is starting so small that your brain barely reacts.

Give one genuine compliment and walk away. "I like your jacket." "That dog is great." You are not starting a conversation. You are giving your brain a stranger moment that ends well, with no pressure to keep talking.
Add one light line after the compliment. "Where did you find it?" Then let it go wherever it goes. If it ends in ten seconds, that still counts.
Stay for a longer conversation. Once the first two steps feel almost boring, let a conversation run a few minutes.

Move up only when your current step feels boring. Boring is the sign that the alarm stopped going off.

Stop grading what you said

Most people walk away from a blank moment and grade it. Too short. Too awkward. Should have asked a better question. That grading teaches your brain the moment was a failure, which makes the next blank moment more likely.

Use one question instead: did I do the rep? If you said something, it counts. A short answer counts. The rep is the win, not how smooth it sounded.

I used to be the guy who spent four hours walking around Chicago trying to work up the nerve to talk to one stranger. What finally changed it was not a list of topics. It was small reps every day and refusing to judge them.

I put the whole method into a short field guide called The Confidence Download. It has the three step ladder, the one question scoreboard, and a 90 day tracker so you can see your reps add up. If you want it, it is here: https://payhip.com/b/oxt6n

And next time your mind goes blank, try this: give one honest compliment, smile, and leave. Then notice that nothing bad happened.

Why You Keep Waiting for the Right Moment to Speak Up

Christopher Jakob — Sun, 01 Nov 2026 15:08:34 +0000

You are in a meeting and you have a good point. You can feel it sitting right there. You just need the right moment to jump in.

So you wait for a pause. Then someone else takes the pause. You wait for the topic to come back around. It moves on. Ten minutes later a coworker says almost exactly what you were thinking, and everyone nods.

You leave the meeting annoyed at yourself, and a little more convinced that you are just not a speak up kind of person.

You are not missing some talent other people have. You are waiting for a signal that your brain was trained never to give you.

Your brain is waiting for proof it is safe. It will never find enough.

There is a part of your brain called the reticular activating system, the RAS. It filters what you notice and decides what deserves your attention. After enough moments where speaking up felt uncomfortable, that filter starts treating every opening as risky.

So when you look for the right moment, the RAS scans the room for reasons it is the wrong one. Your boss looks busy. The last person got a short answer. Your point might sound obvious. Every pause comes with a reason to let it pass.

The perfect moment never arrives because the part of you judging the moment is the same part that wants you to stay quiet.

Waiting feels safe, but it trains the fear.

Every time you wait and the moment slips by, your brain logs it as a win. Nothing bad happened. You stayed safe. Next time, the urge to wait is a little stronger.

That is why speaking up does not get easier on its own. You are not getting more practice talking. You are getting more practice waiting.

Make the first move small and early

You change this the same way the filter got trained in the first place: with new experiences, in the right order, small enough that you actually do them.

Speak in the first five minutes. It does not need to be a big point. A short agreement, a question, or saying "that makes sense, can I add one thing later" counts. Early is easier than late because the stakes have not built up yet.
Say one sentence, then stop. You do not need a full speech. One clear sentence gets your voice into the room. You can add more if people ask.
Build up to your real point. When speaking early starts to feel boring, start leading with the point you actually came to make.

Move up only when the current step feels almost boring. Boring means your brain stopped flagging it as a threat.

Change what counts as winning

Most people judge a meeting by how well their point landed. That is a scoreboard you will lose on most days, because so much of it is out of your control.

Use one question instead: did I say it? If you spoke, it counts. If the point was not perfect, it still counts. The rep is the score, not the reaction.

Outside of meetings, I used to be the person who spent four hours walking around Chicago trying to work up the nerve to talk to one stranger. What changed it was not waiting until I felt ready. It was doing small reps every day and refusing to grade them.

I wrote the whole method into a short field guide called The Confidence Download. It has the three step ladder, the one question scoreboard, and a 90 day tracker so you can see the reps add up. If you want it, it is here: https://payhip.com/b/oxt6n

And in your next meeting, try just one thing. Say something in the first five minutes. Then notice that nothing bad happened.

Why You Replay Every Conversation for Hours Afterward

Christopher Jakob — Sat, 31 Oct 2026 14:19:57 +0000

You say something slightly awkward to a coworker in the kitchen. The whole thing lasts maybe two minutes. They probably forgot it before they got back to their desk.

You did not. You replayed it on the drive home. You replayed it while making dinner. At midnight you were still rewriting what you should have said.

If you do this, you are not broken and you are not overly sensitive. Your brain is doing exactly what it was trained to do. The good news is that training can change.

Your brain is collecting evidence, and it only keeps one kind.

There is a part of your brain called the reticular activating system, the RAS. It filters everything you experience and decides what is worth your attention. After enough uncomfortable conversations, that filter starts treating social moments as risky and scanning them for proof that things went badly.

So after every interaction, it goes looking. It skips the part where the other person smiled. It skips the ten normal sentences. It locks onto the one pause, the one word that came out wrong, and it plays that clip on repeat. Every replay teaches it a little more firmly that talking to people is dangerous.

The replay is not reflection. It is a scoreboard you can never win.

Most of us think replaying a conversation helps us improve. It almost never does. You are not learning anything new on the fortieth replay. You are just grading yourself on a test that already ended, using a grader that only marks mistakes.

That is why I tell people to change the scoreboard. Instead of asking how well did that go, ask one question only: did I do it?

If you started the conversation, it counts. If you gave the compliment, it counts. If you stayed one minute longer than usual, it counts. The result is not your score. The rep is.

How to rebuild the evidence the right way

You quiet the replay by giving your brain a pile of new evidence that conversations end fine. Small ones, in the right order.

One genuine compliment. To a cashier, a neighbor, a coworker. No follow up. It takes five seconds and it almost always lands well.
Compliment plus one light question. When the first step feels boring, add a simple question about whatever you noticed.
A slightly longer conversation. When that is easy too, let it run a minute or two before you wrap it up.

Move up only when the current step feels almost boring. Boring is the sign your brain stopped flagging it as a threat.

What to do when the replay starts anyway

It will still start sometimes. When it does, say out loud or in your head: that counted. Then name one thing that went fine, even something tiny like they laughed or they answered my question. You are not lying to yourself. You are just making the filter look at the part it keeps skipping.

I used to be the person who spent four hours walking around Chicago trying to work up the nerve to talk to one stranger, and then replayed that one conversation for days. What changed it was not thinking harder about it. It was doing small reps every day and refusing to grade them.

I put the whole method, the three step ladder, the one question scoreboard, and a 90 day tracker, into a short field guide called The Confidence Download. If you want the full version, it is here: https://payhip.com/b/oxt6n

Either way, the next time you catch yourself replaying a conversation, try asking just one thing. Did I do it? If yes, you won.

You say yes to deadlines you know are impossible. Let's fix that.

Christopher Jakob — Fri, 30 Oct 2026 17:43:03 +0000

You get asked "can you have this done by Friday?" and you say yes, even though you already know it needs two weeks. I will show you why your brain does that and the small daily rep that gets you to say "here is what Friday actually gets you" instead.

If you keep agreeing to impossible deadlines, you are not weak and you are not bad at estimating. You are protecting yourself from a moment of discomfort, and paying for it with three weeks of stress.

What you actually hear

Your lead says: "Any chance this ships Friday?"

What you hear: "Good engineers say yes. If you push back, you're the slow one. You're the problem."

So you say "should be fine." Then you work nights, cut the tests, ship something shaky, and spend next week fixing it. Or you miss the date anyway, and now you have the conversation you were avoiding, just later and worse.

Here is the part that took me years to see: the question was a question. Your lead wanted information. You gave them a comforting story instead.

Why it hits so hard

I don't believe you build confidence. I believe you unhide it. You already have the knowledge to say "that's two weeks." You did the math in your head before they finished the sentence. What is missing is not skill. It is permission to let someone be briefly disappointed in you.

Your brain runs a selective filter called the reticular activating system, the RAS. It decides what gets your attention, and it learns from what life fed it. Maybe a parent got angry when you said no. Maybe an old manager rolled their eyes the one time you pushed back. Your filter took notes: disagreeing with someone in charge equals danger.

So now, in a planning meeting, the filter skips past the facts and locks onto the risk of a frown. You cannot logic your way out of that. "Just be honest" bounces off, because the filter does not run on logic. It runs on experience. So you feed it new experiences.

The daily rep: compliment a stranger

Once a day, give one genuine, specific compliment to a stranger. Nice boots. Great laugh. That dog is a legend. Say it, smile, keep walking.

I know that sounds unrelated to sprint planning. It is the same muscle at low stakes. You are saying something true out loud, to someone whose reaction you can't control, while your body braces for it to go badly. The first few will spike your heart rate. Then they stop.

The rule that makes it work: the win is the action, never the result. They ignore you, win. They light up, win. You only managed to think it, still a win. If you only count the ones that go well, you are training the old program that says speaking up only counts when people approve. The rep is the point.

That is rung one of a short ladder:

Genuine compliments to strangers
Compliment plus a quick "how's your day going?"
A longer conversation, no agenda

Move up only when the current rung stops spiking you.

Bring it to your deadlines

Once the stranger reps feel easy, run the same reps at work.

Buy yourself ten seconds. You do not have to answer on the spot. "Let me look at it and get back to you in an hour" is a complete sentence.

Trade, don't refuse. Never answer with a flat no. Answer with options. "Friday gets you the API and the happy path. Full error handling and tests is the following Wednesday. Which do you want?" Now you are not the blocker. You are the person who made the tradeoff visible.

Name the risk once, in writing. One short message: "Heads up, the Friday date assumes the auth team's change lands by Tuesday. If it slips, we slip." You are not complaining. You are giving your lead the information they asked for.

Count the sentence, not the reaction. Same rule as the compliments. You said the real number out loud, win. They pushed back, still a win. Their job is the decision. Your job is the truth.

What Athena taught me about honest numbers

On Athena, edge sensors ran a local model, and when it flagged something significant it shipped context from before, during, and after the event back to AWS so the models could be retrained. That only worked because the data was honest. If the sensors had quietly dropped the messy events to make the numbers look clean, the models would have gotten worse, and nobody would have known why.

Your estimates are field data for your team. When you shave two weeks down to three days to avoid a frown, you are dropping the messy events. The plan looks clean, and it is wrong.

You already know the real number. Old training just taught you that saying it is the dangerous part.

Your mission this week

Compliment one stranger a day for seven days.
The next time someone asks for a date, say "let me check and get back to you" before answering.
Answer one deadline request with two options instead of a yes.
Write one short risk note to your lead about something you have been quietly worried about.

Then tell me in the comments: what is the deadline you said yes to this year that you knew was impossible the moment you heard it?

Why Rehearsing What to Say Makes You Freeze Even Harder

Christopher Jakob — Fri, 30 Oct 2026 14:15:23 +0000

Before almost every conversation that mattered, I used to write a little script in my head. What I would say first. What they would probably say back. A clever line ready for the pause.

And almost every time, the conversation went somewhere I had not planned within ten seconds. The script was useless, my mind went blank, and I stood there feeling worse than if I had prepared nothing at all.

If that sounds familiar, it is not because you are bad at preparing. It is because scripts work against the thing you are actually trying to build.

A script tells your brain the conversation is dangerous.

There is a part of your brain called the reticular activating system, the RAS. It filters everything around you and decides what deserves your attention. When you have had a lot of awkward conversations, that filter learns to scan for signs that things are going wrong.

When you rehearse every line, you are quietly agreeing with it. You are saying this situation is so risky that I cannot be trusted to just respond. So the moment the conversation leaves your script, the filter hits the alarm, and the blank mind you were trying to avoid shows up right on time.

Confidence is not having the right words. It is not needing them.

The people who seem relaxed in conversation are not pulling from a better script. They have simply had so many ordinary conversations where nothing bad happened that their brain stopped treating talking as a threat. They are free to listen, so they respond to what is actually being said.

You get there the same way they did. Not with better lines, but with more small experiences, in the right order.

Start with one genuine compliment. To a barista, a coworker, someone in line. No follow up needed. The whole point is a tiny interaction that goes fine.
Add one honest question. When compliments start to feel boring, follow one with a light question about whatever you noticed.
Let it run a little longer. When that is easy, stay in the conversation for a minute or two before you wrap it up.

You only move up when the current step feels almost boring. Boring means your brain has stopped flagging it as danger.

What to do instead of rehearsing

If you have something important coming up, like an interview or a meeting, prepare your points, not your lines. Know the two or three things you want the other person to understand. Then let the words come out however they come out.

And on the days in between, get your reps in. Ten small, low stakes interactions a day will do more for your next big conversation than an hour of rehearsing in the shower.

I once spent four hours in Chicago trying to work up the nerve to talk to a single stranger, and I had a script ready the entire time. The script never helped. The reps did.

I put the whole method, the three step ladder plus a 90 day tracker, into a short field guide called The Confidence Download. If you want the full version, it is here: https://payhip.com/b/oxt6n

Either way, try one compliment today and skip the script. See what happens.

Why Your Confidence Disappears the Day After You Finally Feel It

Christopher Jakob — Tue, 27 Oct 2026 18:01:54 +0000

You know the feeling. You go to an event, you push yourself, and somehow it works. You talk to three people, one of them laughs at your joke, and you walk out thinking this is it, I finally cracked it.

Then two days later you are back in a meeting with your stomach in a knot, saying nothing. It feels like the confidence was borrowed and someone came and took it back.

I used to think that meant something was wrong with me. I once spent four hours in Chicago working up the nerve to talk to one stranger. When I finally did it, I felt amazing for about a day. Then it was gone, and I was right back where I started.

Here is what I eventually figured out.

Your brain is not keeping score of your best night. It is keeping score of your average day.

There is a part of your brain called the reticular activating system, the RAS. Its job is to filter the flood of information around you and decide what is worth noticing. If you have spent years having awkward conversations, it has been trained to notice every sign that a conversation is going badly. The pause. The glance at a phone. The polite smile that might mean they are bored.

One great night does not retrain that filter. It is one data point against thousands. Your brain files it away as a lucky exception and goes right back to scanning for danger.

What actually moves the filter is volume.

Not intensity. Volume. Small, repeated experiences where nothing bad happens. That is what teaches your brain that talking to people is normal and safe.

So instead of saving up for one big brave moment, I started doing small reps every single day:

Give a genuine compliment. To a barista, a coworker, a stranger in line. That is the whole rep. You do not need a conversation after it.
Add one line. Once compliments feel boring, follow one with a light question. "That jacket is great, where did you get it?"
Stay for a minute. Once that feels easy, let the conversation run a little longer before you wrap it up.

The rule is simple. You only move up a rung when the current one feels almost boring. Boring is the signal that your brain has stopped treating it as a threat.

Why this sticks when the big night did not

Ten small reps a day is around three hundred a month. Your brain cannot write off three hundred experiences as luck. At some point the filter starts noticing different things: the smile back, the person who was happy you said something, the conversation that just went fine.

That is when confidence stops feeling borrowed. It stops being a mood you get after a good night and starts being your normal.

Count reps, not results

The other trap is grading yourself on how each conversation went. Did they like me? Was that weird? That keeps your brain in danger scanning mode. The only thing worth counting is whether you did the rep. Ten done is a win, no matter how any single one went.

If you want the full system, I put it into a short field guide called The Confidence Download. It covers how the filter gets locked, the three step ladder in detail, the only scoreboard worth keeping, and a 90 day tracker with checkpoints at day 30, 60, and 90. You can grab it here: https://payhip.com/b/oxt6n

But even if you never read it, try this tomorrow: one genuine compliment to someone you would normally walk past. Then do it again the next day. The confidence you felt on your best night is not gone. It just needs more than one night to stay.

You skip jobs unless you meet every requirement. Let's fix that.

Christopher Jakob — Tue, 27 Oct 2026 17:41:32 +0000

You read a job post, you match seven of the ten requirements, and you close the tab. I will show you why your brain does that and the small daily rep that gets you to hit "apply" anyway.

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 walked into rooms where I was clearly the least qualified person there, and I have also talked myself out of roles I would have crushed. The second one cost me more.

If you keep skipping applications, you are not lazy and you are not unqualified. Your filter is running the wrong math.

What you actually read

The posting says: "5+ years of Kubernetes experience preferred."

What you read: "Real engineers have this. You don't. Don't embarrass yourself."

That gap is the whole problem. A job post is a wish list written by a hiring manager in a hurry, sometimes copied from an old post nobody updated. You read it like a legal contract. So you only apply to roles you are overqualified for, you get bored in six months, and the cycle repeats.

Why it hits so hard

I don't believe you build confidence. I believe you unhide it. The same developer who will happily pick up an unfamiliar library on a Tuesday and ship with it by Friday will refuse to apply for a job that lists that library. The skill to learn is already there. What changed is that now someone might say no.

Your brain runs a selective filter called the reticular activating system, the RAS. It decides what gets your attention, and it learns from what life fed it. Maybe you got picked last. Maybe you applied for something big once and heard nothing back. Maybe someone told you to stay in your lane. Your filter took notes: reaching equals rejection, and rejection equals danger.

So now, when you read a job post, the filter skips the seven things you can do and locks onto the three you can't. You cannot logic your way out of that. Telling yourself "just apply, what's the worst that can happen" bounces off, because the filter does not run on logic. It runs on experience. So you feed it new experiences.

The daily rep: compliment a stranger

Once a day, give one genuine, specific compliment to a stranger. Nice jacket. Great laugh. That's a cool bike. Say it, smile, keep walking.

I know that sounds unrelated to a job hunt. It is the same muscle at low stakes. You are making an offer with no control over whether it gets accepted, while your body braces for a no. The first few will spike your heart rate. Then they stop.

The rule that makes it work: the win is the action, never the result. They ignore you, win. They light up, win. You only managed to think it, still a win. If you only count the ones that go well, you are training the old program that says reaching out only counts when people say yes. The rep is the point.

That is rung one of a short ladder:

Genuine compliments to strangers
Compliment plus a quick "how's your day going?"
A longer conversation, no agenda

Move up only when the current rung stops spiking you.

Bring it to your job search

Once the stranger reps feel easy, run the same reps on applications.

Count what you have, not what you lack. Before you close a tab, write down every requirement you meet. If it is around 60 percent, you apply. That is the rule. No debate with yourself.

Translate the gaps. "No Kubernetes" becomes "I deployed containers with Docker Compose and I learn infra tools fast. Here is one I picked up in two weeks." A gap with a learning story is not a gap. It is proof you grow.

Apply to one stretch role a week. Not ten. One. A role that makes your stomach tighten a little. That stomach tightening is the rep.

Count the send, not the reply. Same rule as the compliments. You hit submit, win. They ghost you, still a win. Your job is the action. Their job is the decision. Don't do their job for them by rejecting yourself first.

Ask one real person. Message one engineer at the company: "I'm applying for the backend role. What does the team actually use day to day?" Most people answer. Each answer teaches your filter that reaching out is safe.

What Athena taught me about "not ready"

On Athena, edge sensors ran a local model. The model was never perfect. When it flagged something significant, it sent context from before, during, and after the event back to AWS so it could be retrained. If we had waited until the model was perfect before deploying it, it would never have gotten better, because the field data was the thing that made it better.

You are the same. You don't get ready and then apply. You apply, interview, get feedback, and that is what gets you ready. Waiting until you check every box is like keeping the model in the lab forever.

You already know how to learn the missing thing. Old training just taught you that asking for the chance is the dangerous part.

Your mission this week

Compliment one stranger a day for seven days.
For every job post you skip, write down which requirements you actually meet.
Apply to one role where you meet about 60 percent of the list.
Rewrite one "gap" in your resume or cover letter as a learning story.
Message one engineer at a company you want to work for.

Then tell me in the comments: what is the requirement that always makes you close the tab, and how much of it could you learn in a month?

Why You Are Fine With Friends but Freeze With Strangers

Christopher Jakob — Sat, 24 Oct 2026 22:05:21 +0000

Plenty of people tell me the same thing. With friends they are funny, quick, relaxed. Put them next to someone new at a party, a meeting, or a coffee line, and their mind goes quiet and their chest gets tight.

If that is you, nothing is broken. You are not secretly an introvert who should give up on new people. You have a filter problem.

The filter in your head

Your brain has a system called the reticular activating system. Its job is simple: decide what deserves your attention out of everything around you. It learns from experience. Whatever you have seen often, and whatever felt important, it shows you more of.

With friends, you have hundreds of good memories stacked up. Your filter expects things to go fine, so it shows you the laughs and the easy moments.

With strangers, the stack is small, and it is usually lopsided. Maybe a few awkward moments from years ago that you replayed so many times they now feel like the whole story. So the filter does its job. It scans for the pause, the odd look, the sign that this is going badly. You are not imagining danger. You are seeing exactly what you trained yourself to see.

Why advice like "just be yourself" fails

You cannot think your way out of a filter. Telling yourself to relax with strangers is like telling yourself to stop noticing red cars after you bought a red car. The filter does not take orders. It takes evidence.

That is the good news, too. Because if evidence built it, new evidence can rebuild it.

Building new evidence in the right order

The mistake most people make is starting too big. They try to walk into a networking event and work the room. It goes badly, the filter collects one more bad memory, and the lock gets tighter.

Start smaller than feels useful:

Give one genuine compliment to a stranger. Specific and real. "That is a great jacket." Then move on. No conversation required. This is a rep that almost always goes well, which is the whole point.
Compliment plus one light question. "Great jacket, where did you find it?" Let them talk for a few seconds.
A longer conversation. Only after the first two feel boring do you stay and chat.

Move up a step only when the current one stops making your heart race. Boring means the filter has updated.

What to count

Do not score how well each conversation went. That just feeds the old filter. Count reps. Did you do it? Then it counts. Ten small reps a day for a few weeks gives your brain a brand new stack of evidence about strangers, and the freeze starts to fade on its own.

I once spent four hours in Chicago working up the nerve to talk to a single stranger. The thing that changed it was not a breakthrough. It was reps, in the right order, counted the right way.

I put the full method, the step ladder, and a 90 day tracker into a short field guide called The Confidence Download. If you want the whole system in one place, you can find it here: https://payhip.com/b/oxt6n

Either way, try one compliment today. Just one. That is how it starts.

You take code review comments personally. Let's fix that.

Christopher Jakob — Fri, 23 Oct 2026 17:35:23 +0000

One code review comment can wreck your whole afternoon, even when the comment is about a variable name. I will show you why that happens and the small daily rep that takes the sting out of 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. In the Marines, feedback came loud, blunt, and in front of everyone. You learned fast that a correction was about the task, not about your worth. And I still caught myself in tech reading "nit: this could be simpler" and spending twenty minutes wondering if my lead thought I was bad at my job.

If that is you, you are not thin skinned. Your filter is reading the wrong message.

What you actually hear

Your reviewer writes: "Can we pull this into a helper?"

What you hear: "You don't know what you're doing, and now everyone on the PR can see it."

That gap is the whole problem. The comment is about twelve lines of code. The story you tell yourself is about you. So you either get defensive and argue every point, or you go quiet, accept every change without thinking, and open your next PR with your stomach in a knot.

Why it hits so hard

I don't believe you build confidence. I believe you unhide it. The same developer who calmly walks a junior through their first rebase can feel crushed by a two word comment on their own code. The skill is still there. What changed is how exposed the moment feels.

Your brain runs a selective filter called the reticular activating system, the RAS. It decides what gets your attention, and it learns from what life fed it. Maybe a teacher marked your work in red in front of the class. Maybe an early reviewer was genuinely harsh. Maybe you just grew up where mistakes meant trouble. Your filter took notes: being corrected equals being exposed, and being exposed equals danger.

So now, when a review comes in, the filter skips past the five approvals and the "nice catch" and locks onto the one comment that sounds like criticism. You cannot logic your way out of that. Telling yourself "it's just code" bounces off, because the filter does not run on logic. It runs on experience. So you feed it new experiences.

The daily rep: compliment a stranger

Once a day, give one genuine, specific compliment to a stranger. Great shoes. Love that coffee mug. Your dog looks thrilled to be here. Say it, smile, keep walking.

I know that sounds unrelated to a pull request. It is the same muscle at low stakes. You are putting yourself out there with zero control over how it lands, while your body braces for a bad reaction. The first few will spike your heart rate. Then they stop.

The rule that makes it work: the win is the action, never the result. They ignore you, win. They say thanks, win. You only managed to think it, still a win. If you only count the ones that go well, you are training the old program that says putting yourself out there only counts when people approve. The rep is the point.

That is rung one of a short ladder:

Genuine compliments to strangers
Compliment plus a quick "how's your day going?"
A longer conversation, no agenda

Move up only when the current rung stops spiking you.

Bring it to your PRs

Once the stranger reps feel easy, run the same reps on your reviews.

Read it twice, answer it once. First read is for your feelings. Let them happen. Second read is for the code. Only reply after the second read.

Rewrite the comment in plain words. "Can we pull this into a helper?" becomes "This logic repeats, a helper would make it easier to test." Strip out the tone you imagined and keep the request. Most of the sting lives in the tone you added.

Ask one question per review. "Do you mean a shared helper or one local to this file?" A question turns a judgment into a conversation, and it shows you are engaged instead of hiding.

Push back once, politely, when you disagree. "I kept it inline because it's only used here. Happy to change it if you feel strongly." That one sentence is a huge rep. Each time it goes fine, your filter learns that disagreeing is safe.

Say thanks in the thread. "Good call, that's cleaner." Closing the loop in public trains your brain that feedback ends well.

What Athena taught me about feedback

On Athena, edge sensors ran a local model. When it flagged something significant, it sent context from before, during, and after the event back to AWS so the models could be retrained. Nobody treated that data as an insult to the model. It was the only way the model got better.

Code review is the same loop. A comment on your PR is not a verdict on you. It is training data for you and for the codebase. The developers who grow fastest are not the ones who get the fewest comments. They are the ones who can take a comment, use it, and ship the next PR without flinching.

You already know how to take feedback. Old training just taught you to hear it as an attack.

Your mission this week

Compliment one stranger a day for seven days.
On every review you get, read it twice before you reply.
Ask at least one clarifying question on a review.
Push back politely on one comment you genuinely disagree with.
Thank a reviewer in the thread every time a comment makes your code better.

Then tell me in the comments: what is the review comment that stuck with you the longest, and was it really about you or about the code?