Art

Posted on Apr 19

AI Writes Your App. You Lose Your Job. Good.

Before you close this tab — read the second sentence.

You will not be jobless. You will be work-free. Those are not the same thing.

The Fear Is Real

Let us not pretend it is not.

A developer spends years learning React, Kotlin, Swift, C#.
They build a career on that knowledge.
Then an AI arrives that can generate working code from a sentence.

The fear is legitimate. The question is whether the conclusion is correct.

What AI Actually Does to Development

Here is what happens when you ask an AI to build a React app:

It generates plausible-looking code
The hooks are slightly wrong
The state management is from a blog post written in 2021
The dependency array is missing two items
It works in the demo, breaks in production

React is complex enough that AI-generated code requires a developer
to review, fix, and understand every line. The developer is still fully employed.
They are just a reviewer now instead of an author.

This is not liberation. This is the same job with extra steps.

What Happens With a Simpler Language

SML and SMS are intentionally minimal.

SML has no lifecycle methods. No virtual DOM. No reconciler.
A Column contains children. A Button has text. An ID identifies an element.

Column {
    padding: 24

    Label {
        id: counter
        text: "0"
        fontSize: 48
    }

    Button {
        id: btnAdd
        text: "+"
    }
}

SMS has no async/await. No promises. No event bubbling.
Something happened. Here is what to do about it.

var count = 0

on btnAdd.clicked() {
    count = count + 1
    counter.text = count
}

The entire rule set fits in a single system prompt.
Including the things that trip up AI:

IDs are not strings. Write id: counter, not id: "counter".

Event handlers use dot notation. on btn.clicked(), not onClick.

Variables are global to the script. No closures, no scope confusion.

An AI given this context generates correct Forge apps on the first try.
Not approximately correct. Actually correct. Deployable.

The Loop Nobody Talks About

When AI can generate a complete, deployable app from a description,
the development loop changes:

Before:
  User idea → Designer → Review → Developer → QA → Staging → Production
  Time: weeks

With AI + Forge:
  User describes → AI writes SML + SMS → Push to Codeberg → Live
  Time: minutes

The developer is no longer the bottleneck between idea and reality.

This is where the fear comes from.
This is also where the opportunity comes from.

"But That Means I Lose My Job"

Let us be honest about what that job actually was.

Translating human intent into machine instructions.
That is the core of software development.
A human has an idea. A developer translates it into code the computer understands.

AI is getting very good at that translation.

But notice what disappears when the translation is instant:
the gap between thinking and building.
The weeks of meetings, handoffs, misunderstandings, revisions.
The user who forgot what they wanted.
The developer who built the wrong thing for three months.

That gap was not valuable. It was waste.
We called it "the development process" because we had no other way.

Arbeitslos vs. Die Arbeit Los

There is a distinction that English handles clumsily but the idea is clear.

Jobless — without income, without purpose, without dignity.

Work-free — freed from labor that a machine can do better.

These are not the same condition.

A farmer who gets a tractor is not jobless.
They are freed from breaking their back with a hand plow.
The question is whether they have land to farm with the tractor.

The question for developers is not "will AI take my job?"
The question is "what will I do with the time AI gives back?"

UBI Is the Bridge

Universal Basic Income — BGE in German — is the infrastructure
that makes this transition survivable.

Without it: AI replaces jobs, income disappears, people suffer.
With it: AI replaces jobs, basic needs are covered, time is returned.

The technology already exists to feed, house, and care for everyone.
The question has never been whether we can afford it.
The question has always been whether we choose to.

When a developer no longer needs to spend 40 hours a week
translating requirements into React components —
what does that time become?

What the Time Becomes

Time for the things that were always more important and always got postponed.

Being present with the people you love.

Learning something because it is beautiful, not because it is marketable.

Walking 12 kilometers into a forest to sit with strangers around a fire.

Doing your Kundalini practice before the day starts instead of at 11pm.

Building something because it should exist, not because someone is paying for it.

Software was never the point.

The point was always what software made possible.

The Honest Risk

We should not pretend this transition will be painless.

Between "AI can now do this" and "everyone has UBI" there is a gap.
People will lose income before the safety net exists.
That is real. That is happening now. It should not be minimized.

The answer is not to slow down the technology.
The answer is to build the safety net faster than the disruption spreads.

That is a political problem, not a technical one.
Developers who understand both the technology and its consequences
are exactly the people who should be in that conversation.

What Forge Is Actually For

Forge was built for a world where the gap between idea and running app
is measured in minutes, not months.

SML and SMS are simple by design — not because simplicity is a virtue in itself,
but because a language that a human can learn in a day
is also a language that an AI can generate correctly in a second.

The sandbox is not a technical feature.
It is a commitment: the technology will not be used to harm.
Ahimsa. Do no harm. Written into the license, not the README.

When AI generates a Forge app and a user runs it,
they are running sandboxed code that cannot reach outside its permission boundary.
The AI cannot weaponize the app. The developer cannot weaponize the app.
The architecture enforces the ethics.

That is the kind of technology worth building.

A Different Question

Instead of "will AI take my job?" —

What would you build if the translation problem were solved?

What has been in your head for years that you never had time to make real?
What would you create if creation cost minutes instead of months?

That question is more interesting than the fear.
And the answer to it is what comes after the transition.

Forge is open source.

The tools exist. The time is coming.

Use both well.

Sat Nam. 🌱

Previous posts in this series:

→ We Benchmarked SMS Against C++, C#, and Kotlin. Here's What Happened.

→ From Request to Production in One Push. No Mockup Tool Required.