The first time I watched my own work go out under another man's name, I told myself it was a one-off. A misunderstanding, a bit of office politics, the kind of thing that happens once and then doesn't. I was wrong about the once-and-then-doesn't part. That is really what this is about - not a single grievance, which would be tedious, but a pattern I saw often enough, across enough places, that I eventually had to admit it was the shape of the thing rather than a run of bad luck.
I want to be careful and fair, because bitterness makes for bad writing and worse thinking. Plenty of the consulting work I did over the years was good. It was interesting. It was often exciting - the kind of hard problem that keeps you up in the good way. It paid well. I am not going to stand here and pretend I was mistreated for decades and stayed out of helplessness; I stayed because the work itself was frequently worth staying for. But the work was one thing. What happened around the work was another, and over time the second thing wore down the first.
The pattern, stripped of the specifics that would identify anyone, went roughly like this.
You would do the actual work - the design, the fix, the thing that was difficult and that mattered. And then, somewhere between your doing it and the organisation noticing it, the credit would quietly change hands. Not always dramatically. Sometimes it was as small as documentation you had written being renamed and presented, a few weeks later, as someone else's initiative. Sometimes it was more brazen: a real achievement turning up, almost word for word, on the performance review of a person whose entire involvement had been to sign off on an invoice.
I saw versions of that in more than one place. That is the part that stopped me taking it personally. If it happens once, it is about you, or about one bad actor having a bad year. When it keeps happening, in different rooms, with different people who have never met each other, it is not about you at all. It is about a structure that rewards proximity to the decision over contribution to the outcome - and once you can see that structure, you cannot stop seeing it.
The one that still makes me laugh, in the way you laugh at something that was not funny at the time, was being formally pulled up for doing the right thing.
I had saved a client's documentation where it belonged - in the client's own approved system, in the client's own required format, exactly as the client had asked. This was, by every standard that ought to matter, correct. It was also, apparently, confusing to a manager on my own side, who could not find it in the place he was used to looking. So the confusion became my failing. I was the problem, for having put the customer's records in the customer's own house.
That is a small story, and I tell it because the small stories reveal the operating logic more cleanly than the big ones. The logic was not "did this serve the client." The logic was "did this make the nearest manager's afternoon simpler." Those two things are supposed to point the same way, and in a healthy place they mostly do. But when they diverge, you learn very quickly which one the system actually optimises for, and it is rarely the one painted on the wall behind reception.
There was a breaking point, and like the rest of this it was not unique to one place - I have watched the same move made more than once, which is exactly why I am comfortable describing it in the open.
A manager would sit on maintenance. Not fail to do it through honest overload, which is forgivable and human, but deliberately reject, delay, and quietly bury the steady, unglamorous operational work that keeps a system reliable - hundreds of small tasks, none of them urgent on any given day, all of them essential across a year. And then, when the neglected system began to behave exactly the way a neglected system behaves, the resulting unreliability would be produced as evidence. Look how much trouble this thing is. Look how often it breaks. And that manufactured trouble would become the justification for tearing it out and replacing it with an outside vendor at many times the cost.
The reliability problem was not discovered. It was commissioned. Someone chose the failure, on purpose, because the failure justified a decision that had already been made - and the person who engineered it was, more often than not, praised for decisively solving it. I have watched competent work be starved to death precisely so that its death could be used as an argument. Once you have seen that done deliberately, and seen it rewarded, something in your relationship to the whole arrangement shifts and does not shift back.
I am aware this reads like a catalogue of complaints, so let me say plainly what I actually took from it, because the complaints were never the point.
The lesson was not that people are bad, or that organisations are corrupt, or any other line that lets you off the hook by making it entirely someone else's fault. Most of the people involved were ordinary, and mostly decent, responding rationally to a structure that paid them to respond that way. The lesson was narrower and more useful than outrage: in any arrangement where the value you create can be detached from you and reattached to someone else, eventually it will be - not out of malice, just out of gravity. Value flows toward whoever is positioned to claim it, the way water flows downhill, and no amount of being excellent at the work changes the direction of the slope.
So somewhere in my early fifties I stopped trying to be the best possible water, and started paying attention to the shape of the ground.
Which is, in the least dramatic way I can manage, why I build my own things now.
It is not revenge, and it is not a manifesto about escaping the system - that is usually just a more expensive way of complaining. It is quieter than that. I wanted to spend the second half of my working life in arrangements where the value I make stays attached to the work I did: where if I build something good, the good of it accrues to the thing, and by extension to me, instead of evaporating upward into someone else's review. That is most of what "building your own" actually buys you at this age. Not freedom in the brochure sense. Just a correction to the slope.
I will be honest about the cost, because I am not interested in a founder's victory lap. Building your own thing is harder, lonelier, and far less reliable than a good salary, and anyone who tells you otherwise is selling a course. Some months the old arrangement looks attractive from where I am standing. But I have not once, on even the worst of those months, missed watching my work walk out the door wearing another man's suit.
So the question I would leave you with, if you are somewhere near where I was - good at the work, well-paid, and quietly worn down by everything that surrounds it - is not "should you quit." That is nobody's business but yours. It is this: when you do the best work of your week, where does the credit for it actually come to rest? And if the honest answer is "not with me, and not with the work," how much longer were you planning to keep making it?