Why I Build Products After Work

After a full day of work, building another product may not look like rest.

For me, it serves a different purpose.

Work usually begins with an existing responsibility. A result is needed, a problem has to be solved, or a team needs direction. Building after work often begins with curiosity.

What would happen if this idea were real? Could this repeated task become a tool? Is there a simpler way to turn a thought into something another person can use?

I build because I want to find out.

Curiosity is easier to satisfy by making something

There are many ways to learn. I can read documentation, watch a demonstration, or study how another product works. All of that helps.

But building creates a different kind of learning.

The moment an idea has to work, vague assumptions become visible. The input has to be defined. The output has to make sense. The edge cases appear. A feature that sounded important may turn out to add very little. A small technical choice can create a maintenance problem somewhere else.

Building makes the questions concrete.

This is why I am drawn to prototypes, tools, and small products. They let me learn through consequence. An idea either becomes useful in practice or it reveals what I did not yet understand.

Both outcomes are valuable.

AI lowered the distance between an idea and an experiment

AI changed what I could test on my own.

It did not remove the need to think clearly, understand the user, or make good decisions. It did reduce some of the friction between deciding to explore an idea and producing a first working version.

Questions that once required a long period of preparation can now be explored much faster. I can examine an unfamiliar technical approach, test a small interface, structure a workflow, or identify why something is failing while the original question is still fresh.

That speed matters because curiosity has momentum. When the cost of the first experiment is lower, more ideas can meet reality before they are overdesigned in the mind.

AI has not made every idea good. It has made ideas easier to challenge.

Not every build needs to become a company

There is pressure to treat every product as the beginning of a startup.

If something works, the next questions arrive quickly. Can it be monetised? Can it scale? Who is the market? How large could it become?

Those can be useful questions, but they are not the only reasons to build.

Some projects are experiments. Some exist to solve one problem. Some help me understand a technology. Some are enjoyable because making something from nothing is satisfying.

A project does not need a pitch deck, a revenue target, and a plan to become a large business before it is allowed to exist.

That distinction also makes experimentation more honest. If every prototype must justify itself as a future company, it becomes harder to stop. Time and identity get attached to ideas before they have earned that commitment.

Building for curiosity allows a smaller, cleaner question: did I learn what I came here to learn?

Fun can still produce serious learning

Calling something fun does not make it trivial.

The products I build after work let me practise turning unclear ideas into defined systems. They force me to think about users, inputs, decisions, interfaces, costs, reliability, and maintenance. They expose the difference between a feature that sounds impressive and one that makes the experience better.

Those lessons travel. They improve how I think about work, products, systems, and what is worth building next.

But usefulness is not the only defence I need.

I am allowed to build because I enjoy building.

Not every project needs to become a startup. Not every experiment needs to become an asset. Sometimes curiosity is enough to begin, and learning is enough to make the time worthwhile.