The future, painted.

Scenarios by Balane. The images are concept images by Bria.

Nobody builds apps (2029, Software)

Today, teams write code for months. The day after tomorrow, software takes shape in conversation, in minutes. The machine takes over the typing. Not the deciding, and running it does not get cheaper.

Today

  • Code by description: Developers let AI assistants write functions and only review them. Cursor, Copilot and Claude Code are part of everyday work in many teams.
  • Prototypes the same day: What used to be a sprint now stands as a clickable draft the same afternoon. Whether it holds up in operation shows later.
  • Experts build for themselves: People without a computer science degree build their own internal tools without waiting for IT. Who maintains them once they leave is usually written down nowhere.

What changes

  • You describe instead of build. An app emerges from a conversation about the problem. The software asks back, proposes, builds and tests itself.
  • Being wrong gets cheap. A tool for one week pays off because it costs almost nothing. Whatever does not fit is regenerated. What has to keep running stays expensive: maintenance, security, liability.
  • Deciding becomes the bottleneck. No machine can automate a decision nobody ever made. Whoever does not know what they want gets the wrong thing very quickly.

The story, step by step

  1. A developer floor, today. Code is running on every screen.
  2. On the wall, the backlog. Every card is a wish, and new ones keep coming.
  3. AI already writes code alongside people, who review it. Still, every wish waits for a team.
  4. The day after tomorrow. The desks are gone. A person says what they need.
  5. The software listens, asks back and makes a suggestion.
  6. Then it builds itself. Piece by piece, in seconds.
  7. Before anyone uses it, it tests itself. Every test green, checked against what it understood.
  8. Around every person, whatever they need right now takes shape.
  9. Building now means describing. The machine takes over the typing. Not the deciding.
  10. A tool for one week pays off. Whatever falls apart is regenerated. Whatever has to keep running still costs.
  11. Deciding becomes the bottleneck. If you don't know what you want, you get the wrong thing very fast.
  12. Who still understands your software when the machine that built it fails?

Who still understands your software when the machine that built it fails?

The objection: Maybe running software becomes as cheap as building it. Then the only bottleneck left is knowing what you want. That was always the most expensive part.

The future,
painted.

N° 01 · Software · 2029

Nobody builds apps

01 · Today · Signs that it has begun

  • Code by description

    Developers let AI assistants write functions and only review them. Cursor, Copilot and Claude Code are part of everyday work in many teams.

  • Prototypes the same day

    What used to be a sprint now stands as a clickable draft the same afternoon. Whether it holds up in operation shows later.

  • Experts build for themselves

    People without a computer science degree build their own internal tools without waiting for IT. Who maintains them once they leave is usually written down nowhere.

Draft. Sources to follow.

02 · Tomorrow · 2029 · Concept image

Today, teams write code for months. The day after tomorrow, software takes shape in conversation, in minutes. The machine takes over the typing. Not the deciding, and running it does not get cheaper.

03 · What changes

  1. 01

    You describe instead of build.

    An app emerges from a conversation about the problem. The software asks back, proposes, builds and tests itself.

  2. 02

    Being wrong gets cheap.

    A tool for one week pays off because it costs almost nothing. Whatever does not fit is regenerated. What has to keep running stays expensive: maintenance, security, liability.

  3. 03

    Deciding becomes the bottleneck.

    No machine can automate a decision nobody ever made. Whoever does not know what they want gets the wrong thing very quickly.

04 · The question

Who still understands your software when the machine that built it fails?

The objection Maybe running software becomes as cheap as building it. Then the only bottleneck left is knowing what you want. That was always the most expensive part.

Keep scrolling: N° 02 · Your colleague is an agent

DE/EN

// Vision · 2026
Scenarios, continuously rethought.

////// Manifest

6 scenarios on how software, work, markets and the state will change. Painted with concept images, thought through from 2026 to 2045.

Scroll to enter the valley

Imprint · Privacy

Imprint · Privacy · Deutsch

[························]   0