What if coding became an experience… rather than a method?

It all started with a small daily irritant. Switching users on Ubuntu always took me several clicks — a tiny friction, but enough to break my flow. Not dramatic, but annoying enough to make me want something better.

I had never built a Linux app before. No IDE, no heavy plan. Just an idea, a LLM, and 30 minutes to spare.

Thirty minutes later, a working app was born: ubuntuQuickUserSwitcher / https://github.com/ecappa/ubuntuQuickUserSwitcher

That’s vibe coding. You start with an irritant. You get into the flow. You code without heavy methodology, test, adjust, and share.

And here’s the bigger picture. Innovation isn’t the product of one heroic gesture, but the accumulation of micro-steps. Each solved irritant becomes a building block. Each attempt, an experiment. And even failure becomes material for learning.

This path is never solitary. It’s fueled by exchanges, mentoring, conversations with others. Code itself becomes an ongoing dialogue between idea, experience, and the collective.

Today, this approach is extremely effective at solving very small problems. But tomorrow? Imagine applying the same logic to entire systems.

Heraclitus once said: “You never step into the same river twice.” Code, like life, is a flow. And big applications are nothing more than a web of micro-problems solved, connected together.

This is where spec-driven GenAI enters the scene. Instead of coding “line by line,” we start with specifications — expectations, constraints, behaviors. And the twist? These specs become interactive. We don’t just write them once and forget them. We talk to them, refine them, challenge them. Specs respond, evolve, and act like teammates as much as guardrails.

If today an LLM can turn an idea into an app in 30 minutes, tomorrow it will generate both the code and the spec, compare them against natural language needs, and orchestrate dozens of micro-experiments in parallel. We won’t just code with machines — we’ll co-create in constant dialogue with specs, as if they were part of the team.

Innovation will no longer be a linear project, but a living ecosystem of specs, trials, and interconnected learnings.

Vibe coding is not just about going faster. It’s about a new relationship with code: more fluid, more organic, more human. An experience that starts with a tiny irritant… and could redefine how we create software.

So, what small irritant would you turn into an app if you could code in this flow?