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.
Why Developers Should Post on LinkedIn
You don't post on LinkedIn to become a content creator. You post so that when someone asks 'do you know a developer who can handle this?', somebody thinks of you. It's a long game, and it beats the resume line.
Build the Side Project. Don't Disappear While You Do It.
When the job search stalls, developers build a side project and vanish for three months. Build it, but post the decisions and the bugs along the way. Those are the stories that get you hired.
You Can't Talk About Your Work? Talk About the Decisions
NDA, clearance, or a company that won't let you talk about the product? You don't need to. Every project is full of decisions that aren't the project, and how you made them is what a senior dev or hiring manager actually wants to see.
You Have More to Post About Than You Think
The most common thing developers tell me is they don't know what to post on LinkedIn. You fixed something this week, made a tradeoff, screwed something up. That's the post. Write five sentences and hit publish.
Hiring Managers Have a Problem Too
Developers are upset about the job market, but hiring managers are drowning in hundreds of AI-written resumes and would rather interview someone they already know. Become known before the job opens.
More Skill Doesn't Fix Being Invisible
Developers prep for the next job with more certs, more side projects, more LeetCode. If the real problem is that the right people don't know what you can do, more skill doesn't fix it. Ask who needs to know what you already know.
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.
Six days. One action each day. Five things you'll actually have at the end.
- Get clear on your direction
- Build your visibility
- Create career leverage
- Become in-demand
You're not being overlooked because you're not good enough.
You're being overlooked because nobody knows what you're good at.
Six days. One action each day. At the end you'll have a short list of people who should know who you are, and you'll have started the conversation with the first of them.
- Days 1–2: take inventory of what you've already done that nobody outside your team has seen
- Days 3–4: pick one place to be visible and put three pieces of proof there
- Days 5–6: turn that into conversations with people who make decisions
Free. Six emails. Unsubscribe whenever. No hard feelings.
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.