Your career isn't broken.
You're just playing the wrong game.
Great developers aren't struggling because they can't code. They're struggling because nobody ever taught them how careers actually work.
The old game
- Write good code.
- Keep your head down.
- Work hard and wait.
- Apply when you need something.
Result: Burnout, frustration, and hoping for luck.
The new game
- Become known.
- Create receipts.
- Build relationships early.
- Make opportunities find you.
Result: Leverage, freedom, and career optionality.
You don't have a skills problem. You have a visibility problem.
The market can't reward you for value it can't see. Let's fix that.
Notes from the road, written as I go.
Short pieces on how developer careers actually work: visibility, positioning, leverage, and the parts nobody explains.
I've Forgotten More Than You'll Ever Know
Senior developers often say they don't know much, then spend 15 minutes explaining the auth and caching behind their 'simple' API. Run it recursively: what do you do, and what do you need to know to do that? The lessons you've forgotten are gold to everyone behind you.
Done Is Better Than Planned
A guitarist friend spent a week chasing a take he'd already nailed on day one. Developers do the same with posts about their work: the first honest draft is usually the best, and polishing it for days kills the habit. A recording lives for years. A post doesn't.
"I'm Not Good Anywhere but Here"
Developers with 10+ years in one codebase often treat it as a liability: old stack, short resume, behind on the latest. It's depth most developers never get. Write down the 3 hardest problems that system taught you to solve. That's your story.
The Receipt Gap: Your Memory Runs Last-In, First-Out
Developers move from problem to problem, so at review time the only wins we remember are the recent ones. The Receipt Gap is the distance between the value you delivered and the value anyone can point to. Close it with one line every Friday.
AI Doesn't Take the Responsibility
AI lets me write an order of magnitude more code than by hand. When it breaks at two in the morning, the model isn't the one responsible. More output means more ownership, not less.
Write Episodes, Not Movies
One LinkedIn post turns into seven sections and two hours because you're trying to make a movie. Make sitcom episodes instead: one queue that was the wrong choice, one boundary developers get wrong. The larger story tells itself.
I'm Tony. I've been the invisible developer.
Twenty-five years building software for companies that couldn't afford downtime. Architecture, distributed systems, and the calls that come in when something is breaking under load.
For most of that time I was good at the work and quiet about it. The opportunities that changed my career didn't come from getting better. They came from people knowing what I was good at before they needed it.
Developers Road is what I wish someone had handed me twenty years earlier.
- Microsoft MVP, .NET and Azure
- .NET Foundation member
- Speaker and workshop presenter, VS Live
- Writing to around 8,000 developers
You don't need more luck. You need a better system.
Twice a week. One idea, one 15-minute action, and the reasoning behind both.
- Get clear on your direction
- Build your visibility
- Create career leverage
- Become in-demand
Two emails a week on getting known
for the work you already do.
Tuesday is the working issue: one topic, the thinking behind it, and a 15-minute action you take out in the world, not in a notes file. Friday is shorter: what I'm chewing on this week, plus what's new from Developers Road. Reply to either one and it comes straight to me.
- Tuesday: one topic, one lesson, one 15-minute action that gets you a small win
- Tuesday: a real story from the DMs, or an industry shift explained
- Friday: a thought piece and what's new across DR
Free. 2 emails a week. Unsubscribe whenever.
I'm Tony Champion — 25 years building software, Microsoft MVP, and I write to about 8,000 developers about getting known for the work they already do.