“I thought my code would speak for itself.”
I’ve heard versions of that a lot lately. Good developers who did what we were all taught to do: work hard, get the certs, keep your head down. Then they assumed the company would notice and take care of them.
Here’s the part nobody warns you about.
The better you get, the more invisible you become.
Fewer bugs. Fewer escalations. Fewer surprises. Which turns you into the developer nobody has to worry about. And people don’t think much about the things they don’t have to worry about.
That’s the silent career killer. Not underperforming. Performing so reliably that you disappear.
It costs both sides
If your company doesn’t know what you’re actually worth, they’re guessing. They guess low. That’s not malice, it’s just what happens with missing information.
Meanwhile your value is your career. The more your company sees it, the more opens up inside. The more other people see it, the more finds you without you looking.
What to make visible
Not your output. The part that never shows up in a commit:
- How you think
- How you break down a problem
- The decision that saved six months of rework
- The direction change that stabilized the product
- The thing you argued against and were right about
Start with one. Pick a decision you made this quarter and tell someone outside your team why you made it that way. Not what you built, but why you chose it.
In a world where AI is commoditizing the code, how you tackle the situation is the part it can’t take.