When you build a tool for yourself, why do you need to share it with everyone?
It helps your productivity. It makes you “irreplaceable.” Fine. But sharing builds influence. Why do you need influence? To get promoted? Why get promoted? More money. Follow the chain far enough and it always ends at money. Somehow that answer never satisfied me.
I don’t build tools to share. I build because I don’t like how things work. Something is missing, nobody assigned it to me, I just wanted it to exist.
But here’s the messy part. The line between my time and work time is blurry. My employer pays for my hours, and some of those hours go into the tool. Then again, the tool ends up used for work too. So whose tool is it? Whose time was that?
My manager pushes me to release fast. He says timing matters. Every day the tool isn’t out, another team might ship it first, and my credit for it drops to zero. For a long time my answer was: so what? In my situation, one slow year isn’t the end of the world, and the reward for a great year isn’t life-changing either. If I have little to lose, why rush?
Then I asked myself: am I just procrastinating? Is the deadline the only thing keeping me honest?
I don’t think so. Procrastination means delaying something you’ll regret delaying, and I don’t regret this. What I actually want is simpler: pure innovation without a timeline. Chase the interesting thing until it’s real, not until the quarter ends. How wrong is that?
A lot of good technical work came out of exactly that mode, I told myself. Deadlines make delivery faster. They rarely make ideas better.
I almost stopped thinking there. Comfortable conclusion: I don’t care about credit, the stakes are low, I’ll work at my own pace. Case closed.
But one small fact kept bothering me. I’m building with company resources.
That one fact unraveled the whole argument. Look at what actually funds my way of working: the resources, the slack time, a manager who tolerates “no timeline,” nobody counting my hours. All of that is discretionary. Someone upstream keeps approving it. Why? Because my record looks good.
So I had credit wrong. It’s not a prize I can refuse. It’s the budget line that pays for my freedom. I was saying “I don’t care about credit” while spending it every single day. It also means the chain in my second paragraph was wrong. Followed all the way, it doesn’t end at money. It ends at getting to work the way you want. I had just stopped following it too early.
Now my manager’s warning reads differently. “Ship before another team does” isn’t about my bonus. His claim is that credit is winner-take-all: if another team ships first, mine doesn’t drop a little, it drops to zero. Is that a law of nature? Probably not. But it matches what I’ve seen here, so I’ll take it as how this place works. And when the record drops, the first things cut are the discretionary things. The resources. The tolerance. The freedom to wander. He might honestly mean “I want the best for you,” where the best is protecting the arrangement that lets me work the way I like, and the only way he can protect it is by pointing at things I’ve actually shipped.
So was the problem too much autonomy? No. It was autonomy running on old credibility, with no recent deposits.
The fix isn’t rushing. It isn’t learning to love the scoreboard. It’s noticing that shipping, occasionally, is the deposit that keeps the account open. Shipping is also the only way to find out if the thing actually works outside my head. Innovation without a timeline is a mode. Innovation that never meets reality is just a story I tell myself.
I still build because things annoy me. I still rest after projects. I still don’t chase the credit grade. But every so often, something I built has to leave my machine and meet the world.
That’s not selling out my mode. That’s paying its rent.
And if you also have freedom at work that nobody seems to be counting, maybe ask the question I skipped for too long: what is quietly paying for it? And when did you last make a deposit?