A Large Part of a Programmer's Skill Is Issued With the Company Badge

A line stopped me cold: many people spend a lifetime learning a trade that only counts underneath some platform — taught at school, practiced at a company — and once the environment changes, a large part of it goes straight to zero.

I went through my own ten years against that, and took more hits than I expected.

1. Skill issued with the badge zeroes out when you hand the badge back

I have carried the technical side of one small company for ten years and accumulated plenty of craft. Taken apart, a lot of it was issued by the company.

Which part of a legacy system has a mine buried in it — only I know. Which handshake to use with which supplier — only I remember. Whose desk an approval clears fastest on — only I have a feel for. It all sounds solid, and it is genuinely useful, but it is bolted to this company's walls, and it zeroes out when the badge goes back.

The painful part of changing companies is not rusty skills. It is that this kind of experience cannot travel — not that I forgot how to work, but that the new company has no such wall, so none of my keys fit its locks. And this experience carries an invisible asset with it: whether colleagues remember you, whether your manager trusts you, whether anyone speaks up for you when a process jams. Those follow the badge even more completely, disappearing faster than the technical part.

Worse, it compounds with time. The longer your tenure, the higher the company-specific share tends to be, because the more seasoned you are, the more you get assigned to problems that only exist at this company — moving you further from craft the general market recognizes. That is part of why so many people past thirty-five feel uneasy. Not that their skills failed, but that the badge column of the ledger is too full while the other column has been empty too long.

2. What is actually mine is the part that converts directly to money

The other category is different.

Writing a small tool a stranger can pick up and use. Maintaining an open-source project even with only a few dozen stars. Taking a freelance job and actually delivering it. None of these require me to first prove which company I worked at; the thing itself speaks. The difference is not difficulty. It is whether the craft needs the company as a middleman. The former requires someone to issue a badge, grant permissions, and explain the rules. The latter can set up shop and take orders any time.

Honestly, my share here is low. I had never done the arithmetic before; going through the ledger this time showed it is not modesty, I simply never accumulated in that direction. The open-source project sits unused, and I have never actually closed a freelance job. I can say I now see this ledger clearly. I cannot say I have fixed it.

This path is not free either — the cost is that trust must be stacked up yourself. A company badge comes bundled with an endorsement; you do not have to prove you are reliable. When a stranger pays, what makes them believe you can deliver is whatever you accumulated before: a repository they can open, records they can check, one job you actually finished. That trust accrues far more slowly than learning a new technology, and it is the real reason many people stay inside the badge. Not unwillingness to move — the payback is just slow.

3. AI amplifies this question rather than helping you dodge it

With AI writing code these past two years, many feel the technical barrier collapsed, anyone can ship a product, and maybe the badge matters less.

I think the opposite. AI can instantly hand you a working endpoint or an analysis of a half-debugged error — standardized work, which helps you build up the directly-monetizable column faster. But it cannot tell you why the finance system goes haywire during year-end close. That answer is not in the code; it is in a meeting note from three years ago and in the head of a colleague who already left. AI never worked at your company and cannot learn it. In other words, AI lowered the entry cost for the independently monetizable part while making badge-type experience depreciate faster, because the standardized slice inside it is exactly what gets replaced first.

This question will not disappear because the tools got stronger. It just arrives on the table sooner.

Do the arithmetic before the badge goes back, not on the day it does. I have given myself one extra question: when something is finished, ask whether I could still have pulled it off without the badge. If not, write it down as a debt and look for a chance to repay it. This is not about quitting to go solo. It is about knowing the ledger — without knowing how much of your ability is actually yours, any sense of security is hanging in mid-air.