7 Days, 2000 DM: The First Proof

Some lessons arrive dramatically. Mine arrived as a simple calculation.

The C Course

I was twenty-one, maybe twenty-two.

Before code, there was metal. I was studying mechanical engineering – Maschinenbau – the respectable path. Solid. Predictable. The kind of career that makes parents nod approvingly over dinner.

But the Amiga was still on my desk. And Deluxe Paint had shown me something I couldn't unsee.

So I signed up for an evening course at the Volkshochschule. 60 hours. C programming. Basics.

Not a university degree. Not a bootcamp with a certificate and a career coach. Just a room, a teacher, and the fundamentals of how to tell a machine what to do.

I sat in that room and something clicked.

Not the syntax – though that clicked too. Something deeper. The feeling that I was finally learning the language of the thing I had been drawn to since the Amiga. Since Deluxe Paint. Since the first pixel I ever moved on a screen.

I wasn't studying programming. I was remembering it.

The Sprite Editor

After the course, I built something.

A Sprite Editor.

For those who didn't grow up in the 8-bit era: sprites are the small graphical elements that make up game characters, items, explosions – the visual vocabulary of early video games. Creating them required tools. Good tools were rare.

I built one in about seven days.

Not because someone asked me to. Not because there was a job posting or a client waiting. Because I saw the need, I had the skills, and the idea wouldn't leave me alone until I built it.

Seven days. One developer. No office. No team. No funding.

Just the Amiga, the code, and the same pull I had felt when I first opened Deluxe Paint.

Toolbox

There was a magazine called Toolbox.

In the days before the internet, magazines were how developers shared code. You read articles, you found source code printed on paper, you typed it in yourself if you wanted to use it. It was slow and beautiful and completely serious.

Toolbox wanted my Sprite Editor.

Not just the program – the source code. As an article. Printed. For other developers to read and learn from.

They offered 2000 Deutsche Mark.

The Calculation

2000 DM for seven days of work.

I did the math.

2000 DM per week. That's 8000 DM per month.

As a mechanical engineer – the respectable path, the one that made parents nod – I would have earned significantly less.

And I would have spent my days with metal instead of pixels.

The feeling when I received the money was not excitement. It was not disbelief. It was not even pride.

It was simply:

Logic.

Of course. This is how it works. This is what the numbers say.

The universe had handed me a receipt.

You are on the right path. Here is the proof. Now act accordingly.

The Decision

I stopped studying mechanical engineering.

Not dramatically. Not in a moment of rebellion. Just – the calculation was clear, and I have always trusted clear calculations.

The Maschinenbau path was someone else's logic. Good logic, for someone else.

My logic said: you can build things people need, in seven days, alone, and be paid well for it. You can live from this. You can do this instead of fighting metal that doesn't want to be shaped.

So I chose the pixels.

I chose the code.

I chose the path that had been pulling me since a nineteen-year-old opened Deluxe Paint without a manual and felt – before any understanding, before any skill – that this was it.

What 2000 DM Actually Bought

The money paid for rent. Food. Time.

But that is not what it actually bought.

What it actually bought was permission.

Permission I didn't know I needed until I had it.

Permission to take seriously what I had always taken seriously in private. Permission to call myself a developer when someone asked what I did. Permission to stop pretending that the respectable path was my path.

2000 DM said: the thing you love is also the thing you are good at. And the world will pay for it.

That is a rare and precious message.

Not everyone receives it so clearly. Not everyone receives it so early.

I am grateful I did.

The Article That Never Ran

As far as I know, the Toolbox article was never published.

The source code I sent them, the Sprite Editor I built in seven days – it may never have appeared in print. I don't know what happened. I never followed up.

It doesn't matter.

The lesson was not in the publication. The lesson was in the proof.

I had built something real. Someone had paid real money for it. The math was undeniable.

Everything else – the article, the publication, the recognition – was secondary.

The proof was enough.

The Pattern

Looking back now, I can see the pattern that was already forming:

– Feel the pull before you understand it (Deluxe Paint) – Build the thing that won't leave you alone (Sprite Editor) – Trust the proof when it arrives (2000 DM) – Follow the logic wherever it leads (leave Maschinenbau)

This pattern has repeated itself throughout my entire life.

Forge followed the same pattern. ForgeSTA followed the same pattern. This book follows the same pattern.

The details change. The tools change. The pattern never changes.

Because the pattern is not mine.

I am just the vessel. The pattern belongs to something larger.

And it started with a Sprite Editor and a magazine that may never have printed the article.

Lektion: Ship early. Dein erster Beweis muss nicht perfekt sein. Er muss nur wahr sein.