---
title: "\"I'm Not Good Anywhere but Here\""
url: "https://developersroad.com/notes/not-good-anywhere-but-here"
type: note
status: published
author: "Tony Champion"
published: 2026-10-08
pillar: "developer-career"
topic: "visibility"
tags: ["career", "legacy-systems", "experience", "job-market"]
summary: "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."
---

# "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.

"I'm not good anywhere but here."

I've heard some version of that from several developers lately.

Same company. Same codebase. 10+ years. And they've convinced themselves it's a liability.

The reasons usually sound like this:

- "My tech stack isn't modern."
- "My resume doesn't have enough companies on it."
- "I'm not caught up on the latest and greatest."

Trust me, I get it.

Our industry moves fast. It's easy to feel like you missed the boat and got stranded on the Island of Misfit Languages. Left behind, with no path to catch up.

Here's what you're missing.

Those years in one codebase gave you a depth most developers never get the chance to build.

- You've architected modern solutions on an older stack.
- You've survived more than a few version upgrades.
- You've tweaked, managed, and coded your way through workflows that seemed impossible at first.

That depth is rare. And it's more valuable than you think.

Companies need developers who see the big picture. Not just how the code behaves today, but how it'll hold up a few years down the road. Which patterns stay maintainable. Which ones turn into the thing everyone's afraid to touch.

You know that because you lived it.

"But my stack is old."

You might surprise yourself. Most development skills transcend any one language. Learning a newer stack isn't starting over. It's bolting new tools onto everything you already know.

So if you've been where you are longer than you care to admit, don't hide it.

Start here: write down the 3 hardest problems that system taught you to solve.

That's not a gap on your resume. That's your story.

## Related

- [The Receipt Gap: Your Memory Runs Last-In, First-Out](https://developersroad.com/notes/receipt-gap.md)
- [Qualified Isn't the Same as Understood](https://developersroad.com/notes/qualified-isnt-understood.md)

Read on the site: https://developersroad.com/notes/not-good-anywhere-but-here