Average → Ambitious Engineer: Why I Started This

For a few years I was a perfectly fine engineer. I shipped things. I didn't break prod too often. I got decent performance reviews. My manager had no complaints.

I also had this low-level hum of dissatisfaction that I couldn't quite name.

The moment it cracked open

A junior engineer joined my team. Three months in, she was shipping features I would have taken twice as long to build. Not because she was smarter — she was sharp, but so was I. Because she had no habits of caution.

Watching her work was like watching someone run a race I'd decided to walk.

I went home that evening and thought: when did I decide to walk?

What 'ambitious' actually means

Ambitious, to me, means: operating closer to your actual ceiling. It means closing the gap between what you're capable of and what you're doing. It means not self-limiting by habit.

It's not about working more hours. It's about working with more intention.

Why AI is part of this

Using AI well — actually well, not just for autocomplete — forced me to get clearer on what I was trying to build before I built it. Clearer specs. Clearer thinking. That clarity bled into everything else.

What this series is

Average → Ambitious Engineer is my attempt to document the gap-closing. What I'm trying, what works, what doesn't. Specific things, not vague advice.

I'm not at the destination. I'm writing as someone in the middle of it, who thought some company might help.