A question I get asked often as a programmer is that I should be working on something of my own, building my own business. That with my effort, dedication and talent, I was wasting my time working for other people. Coming from friends who genuinely appreciate what I do, the message has always been the same: you're building someone else's house while renting your own bed. For a long time I didn't know how to answer, not because the question caught me off guard, but because the honest answer was too complicated to fit into a casual conversation. Not to defend myself or justify anything, but to start thinking about how much truth was actually in it. There's an unwritten definition that everyone seems to know. Building something of your own means having a company, a product, a website with your name on it. An Instagram page with "CEO & Founder" in the bio. It means that if you leave tomorrow, whatever you built keeps existing and keeps being yours. This definition is so dominant that almost no one questions it. It's just there, like air, invisible but shaping everything. The problem with this definition isn't that it's wrong. It's that it's incomplete. And when it becomes the only measure that counts, it starts doing damage. Think about it. When you say someone built something, what comes to mind? Probably a founder, an entrepreneur, someone who left their job, took a risk, and created something new from scratch. Now think about the doctor who spent twenty years perfecting a surgical technique. The teacher who shaped three generations of students. The engineer who solved a problem nobody else could crack. The manager who turned a dysfunctional team into one of the best in the company. Did they build something? The answer is yes, just without a logo, without a LinkedIn founding date, without funding rounds. And so, for a lot of people, it barely counts. There's a word for what these people accumulate: craft. And craft is perhaps the most honest form of building that exists, because it can't be inherited, bought, or faked. It's built day by day, job by job, mistake by mistake. The question isn't whether you're building. The question is whether what you're building has enough visibility to satisfy other people's expectations. And that, let's be honest, is a terrible reason to change your life. **Why I work hard and don't regret it** There's something nobody tells you about working intensely for others for years: what stays with you isn't the project you delivered, it's what that project did to you. The way your brain learned to solve problems. The ability to walk into a system you've never seen and know what's wrong before anyone explains it. The patience to handle requirements that keep changing, deadlines that keep tightening, people who don't know what they want but know exactly what they don't want. You don't learn that in a course. You learn it on the job, in the kind of work that demands a lot from you every single day. And yes, there's a difference between effort with purpose and effort that goes nowhere. I'm not romanticising hard work for its own sake, suffering as a virtue. I'm talking about deliberately choosing environments where you get pushed past what you think you're capable of. And many times, those environments exist inside companies that aren't yours, in projects that don't carry your name. I could have started something of my own earlier. But what I wouldn't have learned by doing that, at that point, is worth more than what I would have gained by trying. There's a kind of clarity that only comes from having watched things fail, up close, things that seemed solid. **The trap of "build something or you're wasting yourself"** There's a very specific cultural pressure that equates autonomy with owning a business and working for others with some kind of intellectual surrender. As if choosing a job, even a demanding and well-paying one, were a confession that you don't have enough courage for the rest. It's worth asking who benefits from this narrative. Course platforms sell the idea that anyone can launch a business in 30 days. Accelerators and investors need founders willing to work without a salary for years. The whole ecosystem has an interest in making you believe that the only dignified path is the entrepreneurship path. That doesn't mean building your own thing is wrong. It means the pressure to do so often doesn't come from a genuine interest in you, but from other people's interests wrapped in the language of empowerment. The real cost of starting a business you don't actually want to start is high and rarely talked about. It's not just financial. It's the cost of spending years trying to make something work that you don't fully believe in, while convincing others and yourself that you do. There are far worse ways to waste talent than doing good work for someone else. **What I'm building, then** When people ask what I have to show for years of writing code for projects that aren't mine, the honest answer is: a way of thinking that didn't exist before. Accumulated competence is a non-transferable asset. Nobody can take away what you know how to do. No company that shuts down, no cancelled project, no restructuring erases what has already passed through your brain and changed you. That's yours, completely yours, regardless of who owned the product where you applied it. There's also what gets built in relationships. Trust accumulated with people who have worked alongside you and know what you can deliver. A reputation that forms without you actively managing it, simply through consistency over time. These are invisible structures, but they're among the most durable ones that exist. And then there's something harder to name: clarity about what I want. After working in very different environments, with very different people, on very different problems, I'm starting to know with much more precision which kind of work makes me feel alive and which kind drains me. That self-knowledge, that ability to recognise what actually serves me, is a form of building that doesn't show up on any profile. But it guides everything else. **The justification that never needed to apologise** I didn't write this to convince anyone that entrepreneurship is a bad idea. Or to justify inertia or a fear of taking risks. I wrote it to name something that rarely gets named: the legitimate choice to build slowly, inwardly, without a logo and without an audience, while doing good work on whatever is in front of you. It's not a lack of courage. It's not conformism. It's a different way of taking seriously what you do. The guilt many people feel for not yet having their own business deserves to be examined carefully, because most of the time it isn't yours. It's a borrowed expectation you accepted without questioning. What you're actually building depends entirely on how you define building. And that definition is too important to let someone else make for you.