Building Without Witnesses

There is a part of building something big that almost no one sees.

I'm not talking about the obvious effort. I'm not talking about long hours, little sleep, learning new things or solving hard problems. People can imagine that. Everyone understands that doing something serious costs.

I'm talking about something else.

I'm talking about the loneliness of knowing something exists before the world can see it.

That strange moment when you have a very clear vision in your head, but outside of you it still looks like nothing. Or it looks too small. Or it looks like just a website. Or a garment. Or an idea. Or another obsession. And you know it's not that, but you can't make anyone else understand.

Because it's not finished yet. Because it can't be touched whole yet. Because it still lives too much inside you.

Building in solitude has something almost absurd: you're surrounded by evidence that what you're doing is real, but almost all of that evidence only matters to you.

A folder full of code. An architecture no one has seen. An internal system that works. A design decision that seems minimal, but holds an entire experience. A seam that didn't come out perfect, but taught you something. A domain acquired after months. A data structure thought for a future that doesn't exist yet. A page someone will look at for five seconds without imagining the weeks behind it.

From the outside, much of the time all of that looks invisible.

And that's one of the hardest parts: not that people don't clap, but that there's no easy way to explain the real magnitude of what you're doing without sounding like someone who needs to prove too much.

Because if you explain little, it sounds simple. And if you explain a lot, it sounds like you're trying to convince.

So you learn to keep many things to yourself.

You learn to say 'I'm building a brand' when in reality you're building a whole system. You learn to say 'I'm building a website' when in truth you've spent weeks thinking about identity, trust, product, authenticity, experience, language, operations, errors, edge cases and the future. You learn to summarize a huge architecture in a small sentence so you don't watch the other person lose the thread halfway.

And it's not the other person's fault.

There are things that are only understood when you've been inside.

No one sees all the discarded decisions. No one sees the versions that didn't ship. No one sees the days when something works technically, but doesn't feel right. No one sees when you change a word because that word changes the whole perception of an experience. No one sees when you redo something that was already 'fine' because in your head you know it still wasn't enough.

From the inside, it's often just respect for the vision.

From the outside, it often looks like perfectionism.

Building something of your own also has a pretty uncomfortable side: for a long time you have to believe in a version of reality that doesn't yet have social proof.

There aren't enough customers. There isn't enough recognition. There aren't people saying 'I see it' every day. There isn't an external structure validating that you're not wasting your time.

It's just you, the work and that strange feeling that, even if it's not yet obvious, there's something there.

And that can be beautiful, but it can also wear you down.

Because there are days when you don't need motivation. You need someone to understand the scale. Someone to see what you see. Someone who doesn't stay on the surface. Someone who looks at a small part and can imagine the whole system behind it.

But that doesn't always happen.

Most people only see the result when the result already has shape. When there's already an image. When there's already a product. When there are already numbers. When there's already an easy story to tell. Very few people know how to accompany a work before it looks like a work.

And maybe that's why building in solitude requires a very strange relationship with yourself.

You have to be rational enough not to fool yourself. But irrational enough to keep believing before it's obvious.

You have to look at what you do with severity, correct it, improve it, accept that many parts are still not at the level you want. But at the same time you have to protect the vision from the narrow gaze of the present.

Because the present always tries to reduce things.

It tells you that you still don't have enough. That it still isn't understood. That there still aren't proofs. That maybe you're doing too much. That maybe no one will see it. That maybe all this only matters inside your head.

And sometimes it may be right.

But there's something I've learned building: almost everything that later seems inevitable, at first seemed exaggerated.

Before something has shape, it looks like an obsession. Before something has value, it looks like a waste of time. Before something is respected, it feels too intense. Before something is understood, it usually has to survive a long time without being understood.

That's the hard part.

Not just doing. Sustaining.

Sustaining an idea when it doesn't yet have language. Sustaining a vision when it doesn't yet have an audience. Sustaining a standard when no one is watching. Sustaining an ambition without turning it into a need for validation. Sustaining the silence without mistaking it for failure.

Because building in solitude doesn't mean building for no one.

It means building before others know where to look.

And there's a huge difference in that.

I don't want to romanticize it too much. Solitude doesn't always make you deeper. Sometimes it only makes you more tired, more obsessive or harder to understand. It can also lock you inside your own head. It can make you confuse isolation with judgment. It can make you burden a work with too much personal weight.

But there is a kind of solitude that does build character.

The kind that does something well even though no one sees it. The kind that repeats a part because you know it was wrong. The kind that learns a new skill because the vision demands it. The kind that doesn't depend on immediate applause to keep going. The kind that accepts some stages of a work aren't pretty, epic, or shareable.

They're just necessary.

And maybe that's the hardest thing to explain.

That many times I'm not building one concrete thing. I'm building a structure so many things can exist later.

A foundation. A language. A way of operating. A small world that is still learning to stand on its own.

And when you do that, the reward takes longer. Because you're not only making something that is shown. You're making something that supports what will one day be shown.

That's why sometimes it weighs so much.

Because for a long time the work lives in an in-between zone: too real to abandon, too incomplete for the world to understand.

And yet you continue.

Not because everyone sees it. Not because you always have strength. Not because every day you get an external sign that you're on the right track.

You continue because there's something inside you that has already crossed a point of no return.

Because you know abandoning would be more unbearable than continuing. Because even when you doubt, a part of you recognizes the direction. Because building something of your own doesn't always feel like inspiration; sometimes it feels like responsibility toward a version of yourself that saw something before everyone else.

Building in solitude is that.

Working for a long time on a reality that still doesn't have enough witnesses.

And learning not to need everyone to understand it too soon.

Because if the work is real, one day it will speak better than you.

And maybe then someone will look at the final result and say that everything looked inevitable.

But you will know the truth.

That it wasn't inevitable.

It was sustained.