How I Stopped Waiting and Started Catching Up at Work

I got thrown into a new stack last year and spent the first month waiting. Waiting to feel ready. Waiting to understand everything before I touched the codebase. Waiting until I stopped feeling like an imposter.

It didn't work. The waiting just made the gap bigger.

Here's what changed: I realized I was thinking about the wrong thing entirely.

The Goal Trap

I had this narrative going: "I need to learn React + TypeScript + our monorepo architecture so I can hit my Q1 goals and prove I belong here."

That's goal-oriented thinking. And it paralyzed me. Every decision became: "Does this move me closer to the goal?" That meant I'd skip pairing sessions because they felt inefficient. I'd avoid asking questions that might make me look slow. I'd try to read documentation end-to-end instead of just jumping in.

The problem? I didn't have the identity to support the goal yet. I was still operating as "person who doesn't know this stack." So even when I pushed toward the goal, every micro-decision reinforced that identity.

Identity First, Goals Second

I flipped it. Instead of "get promoted and prove my competence," I asked: Who do I want to be in this role?

For me: someone who asks hard questions. Someone who ships imperfect code and ships it often. Someone who admits gaps without shame. Someone who treats pairing sessions as gold, not distraction.

Once I had that identity locked, the discipline wasn't about willpower anymore. It became: Does this decision reinforce who I want to be?

Scrolling Slack obsessively while waiting for code review? That's not who I am. Jumping into a messy file with 4 modules I don't understand? That is who I am.

Every single choice became obvious.

Massive Imperfect Action

This is the move that actually got me unstuck.

I was sitting at my desk staring at a file with 15 modules, terrified to touch it. The moment I made myself open a PR—even just fixing a typo in a comment—the momentum flipped. Suddenly I had questions. I reached out. Someone reviewed it. I learned. The next change felt less scary.

It's the gym thing: you don't want to go, you force yourself, and five minutes in, the resistance disappears.

I started shipping small PRs constantly. Some were garbage. Feedback came fast. I learned faster.

The discipline here isn't forcing yourself to work harder. It's forcing yourself to work messier, earlier, before you feel ready.

Self-Awareness About Your Actual Blockers

The last piece was brutal honesty. I tracked my actual habits for a week:

• Messaging teammates constantly instead of reading the error message myself first
• Watching tutorials instead of just trying things
• Organizing my notes perfectly instead of getting my hands dirty

These weren't time management problems. They were comfort-seeking habits wearing a productivity costume.

I didn't overhaul everything at once. I replaced one: when I hit a problem, I spend 10 minutes actually reading the error—feeling the discomfort of not knowing—before I ask for help. That habit change alone collapsed my "stuck" time by half.

The Actual Shift

Discipline wasn't a morning routine or a goal spreadsheet. It was three things stacked:

1. Identity first: Who do I want to be in this role? (Not: what do I need to achieve?)
2. Move before ready: Ship the imperfect thing. Momentum kills fear.
3. Replace one bad habit: Not ten. One. The rest follow naturally.

I'm three months in now. I still don't know everything. But I stopped waiting. And somehow, that made all the difference.