← BLOG

We need to make something

Koch curve · infinite edge, finite area

We see a new tool. A film, a game, a working app made with it. Before we have even thought about what we would do with it, we have opened an account. Then, in some WhatsApp group or among friends, that sentence inevitably comes up: “We need to make something with this.”

The urge is not foreign to me. Like many people, I build software to use in my own work. Describing a need, seeing the first working version and then being able to change it the way I want is something I enjoy too. Things I used to have to explain to someone else and have them build, I can now work on directly.

I cannot explain the appeal by the time it saves alone. Seeing that you can do it is a pleasure in itself. Something in your head appearing on the screen, working when you press its button, looking a little more like what you wanted with the next try. Beyond the result being useful, the making has its own reward.

That uncertainty is actually what I like about the sentence "We need to make something with this." We do not know yet what will come out of it. We are not dealing with a job whose justifications are all ready from the start, whose benefit has been calculated and whose outcome is known. We will find it while tinkering.

But the "need to" in the sentence is a little hasty. We have given ourselves a task before we even know the thing we are curious about.

It is a reflex familiar from advertising. A new medium, a new format, an execution that was not possible before. A media-first opportunity. The first question comes right away: "What can we do here?" Sometimes it really is the start of a good idea. A new possibility lets us solve an old problem we had in mind in a different way.

And sometimes, because the possibility is so good, we start looking for a problem to fit it. First we find what we will do, then we write why we should do it. In the presentation, of course, it appears in the opposite order.

In my own projects, the order flips even more easily. There is no client I need to convince. I set the budget, the timing and the brief myself. The meeting needed to start something is quite short. The person making the proposal and the one making the decision are the same person, after all. The idea is automatically very well received.

This freedom is valuable. After years of trying to solve other people’s needs, I want to be able to try out the things that come to my own mind. Nor do I feel like greeting every idea, before it has even started, with the question "Who are we going to sell this to?" I make some things to learn, some to use and some just to see how they turn out. It takes you back to your childhood a little, too.

But once the first working version of an idea appears, my relationship with it changes. A moment ago it was only a possibility. Now it has parts that need fixing.

If only that button were somewhere else. If this screen were easier to read. If it opened one more file type. Since we have come this far, if it worked on the phone too.

Say we have built a small tool to make a recurring task easier. The first version does the job. Then, while using it, we noticed another need and added that too. Then came a new feature connecting the two. Every step has a sensible explanation. In the end, a fairly large app has grown around the small task we started with. The problem the tool was meant to solve is still there. But now there are also more interesting problems to solve while developing the tool.

I do not necessarily see this as a bad development. Maybe a valuable product will come out of that small tool. Maybe I will learn something I can use somewhere else. Or maybe I simply enjoy working on an interface more than the work that interface is meant to make easier. It is interesting that the last possibility seems a little less serious.

Spending three hours with a game is entertainment. Spending three hours on an automation can count as productivity work, even if it has not made anything easier yet. We are at the same computer, the same amount of time has passed. In the second case it is easier to explain ourselves. Even having a settings menu on the screen can make you feel like you are working.

And we really are making something. A file, an app, an image comes out of it. The time we spent has a tangible result. A shareable one, even. Someone else can see it, like it and ask how we made it.

That is why describing the urge to make things as just another habit that distracts us feels incomplete. There is learning here, and skill, and the joy of entering a field we could not get into before. For me, one of the most exciting parts of the work is not having to settle for describing an idea. But something coming out of it does not always mean I have got closer to what I wanted to do.

I think about this while building my own tools. Working on an app and working with that app look very similar from the outside. In both, the screen is on, I am busy, things are moving. Only in one I am doing the actual work, and in the other I am changing the environment I will do that work in.

The second kind of effort has a less clear end. A piece of writing has a point where it is finished. The ways the tool I write it in could be better may never end.

And while all this is going on, other people out there are making other things. I see the app one person built, the film another one made. I enjoy following them. I come across uses I would never have thought of on my own.

But watching them, a strange feeling sometimes comes up. Not having used a possibility I did not even know existed a few minutes ago can look like a shortcoming. I have just learned about something. Falling behind lands in the same minute.

From there it is easy to move on to the question "What could I do with this?" A few minutes later I have started thinking about a new project. There is no space set aside for it in my calendar. But ideas do not check the calendar before they come. Especially when what someone else has made looks really good.

Looking at this from a distance, I cannot draw a conclusion about productivity. Because I want to set my own agenda, and I also love that wandering where I do not know what I will come across. A life in which I judge every new curiosity by how well it fits my current plan does not appeal to me much either.

Sometimes I want to work on something I am glad was not in my plan. Sometimes, while doing work I already love, I get carried away by another possibility. From the outside, both can look the same.

Maybe that is why I feel close to the sentence "We need to make something with this" and laugh at it a little at the same time. There is curiosity in it, enthusiasm, a slight rush. And a shift that has already started while there is still nothing there.

Then I see a really good demo, and I say that sentence too:
"We need to make something with this."