Back to blog
Build in PublicSaaSValidazione

Why Code Is Just a Means: The Manifesto of the New Build in Public Series

Forget polished tutorials: a real logbook begins, made of validated ideas, failures and transparency. To create software that solves problems, not just looks good.

Published May 10, 20263 min read
Why Code Is Just a Means: The Manifesto of the New Build in Public Series

There’s an uncomfortable truth in the software development world, and few have the guts to say it out loud. We are surrounded by beautiful code, clean architectures and over-engineered patterns, but we are short on software that truly serves the business. Software that doesn’t stroke the ego of the creator, but solves a real problem for the end user.

This awareness gave birth to a different project. Not the umpteenth tutorial on how to scale to a thousand users overnight, but a real-time documentary. A video series in which I will build software as a service in public, with total transparency, chronicling every step: from the initial idea to the market launch, through failures, restarts and small, eventual, victories.

The starting point is not the code

The biggest vice in our industry is rushing to write code straight away. You open the IDE, pick the trendiest stack, write clean code and forget the fundamental question: who really needs this solution? The result is a digital graveyard of flawless projects that nobody ever searched for.

In this series we flip the perspective. We don’t start from a technology, but from a market-validated idea. A real problem, discovered by listening to people, analyzing their struggles. Only later, and with a lot of humility, code takes the stage as a simple means, not an end. Because software is not the hero—it’s the tool that sparks a solution and, with a bit of luck and method, creates a company.

Build in Public: no filters, no special effects

This series is not a class where the speaker already has the answer in his pocket. It’s the exact opposite. I will do Build in Public: I will work in front of you with absolute transparency. It means that if an idea doesn’t work I will throw it away without attachment, I’ll share my screen and show the mistakes, the doubts, the forced pivots.

There will be no hidden cuts nor pre-written endings. Viewers will be able to retrace my same steps, and that’s exactly the goal: to turn my own mistakes into lessons for you, so you can avoid them when it’s your turn to build something of your own.

Who is this series for?

For those who are not looking for the get-rich-quick shortcut, but want to understand how to go from a concrete problem to a product that sells. For those who are tired of hearing “write clean code” without ever having validated an idea. For those who want to see behind the scenes of a real entrepreneurial journey—sweaty, uncertain, genuine. In other words, for those who want to build stuff that works.

Now let’s begin. Let’s see what happens.

Video YouTube : https://www.youtube.com/watch?v=WW6NDy3ne7A&t=7s