So We Talk to Machines Now

I remember when ChatGPT first showed up.

Same pattern everywhere: excitement mixed with a bit of panic.
Twitter full of screenshots.
LinkedIn full of takes.

Developers, designers, consultants —
suddenly everyone had done it.
Talked to the machine.

I mostly stayed on the sidelines.
Thought: great. Seen it before. Just another hype.

Then I tried it.

And yeah — this wasn’t just another tool.
It was… something else.

Illustration of a rabbit in a workshop facing a glowing robotic machine that appears activated and interacting with him.

You could treat it like a person
and get something useful back.
Not perfect. But close.

That’s what made it weird.
Not the smartness.
Just the fact that it was there.

Always.
Ready.
Friendly.

No off switch.

Three years later, it’s quieter.
No big moment anymore.

The machine is just there.

Like electricity, Wi-Fi, and bad meetings.
You only notice it when it’s gone.

Too Clean

At first, it was just curiosity.
I wanted to see if it could actually handle code.

So I threw something at it —
something that had been sitting with us for a while.

It had an answer. Just ten seconds later.
Not dumb.
Just… a bit too clean. Too thorough. Too polite.

I went through it.
Damn.

No — it wasn’t better.
It just skipped the whole process.

No overthinking.
No trying things out.
No friction.

I rewrote it.

Not because I had to.
Because I wanted to.

Same feeling as looking at someone else’s draft
and thinking: yeah, good — but not like that.

That’s when it clicked.

The machine isn’t my problem.

It’s a sparring partner.
A mirror.

And sometimes that coworker
who has a take on everything.

Two Worlds

By now, it’s just part of the workflow.

I throw something at it, it throws something back.
Most of the time, it’s fine.

Sometimes a bit too good —
like it solved a different problem than the one I had.

One time I just wanted to clean up a small piece of code.
Nothing special.

It went ahead and wrote half a novel in Python.
Docstrings. Type annotations.
A test setup nobody needed.

I just sat there thinking:
why all this — a one-liner would’ve done it.

That’s the thing.

It’s all about “doing it properly.”
I’m more “just make it work.”

Two worlds.

It wants to show what it can do.
I just want it to run.

I’ve learned to slow it down.
“Keep it short,” I sometimes tell it.

Then it behaves. Mostly.
Still throws in a comment like

// not ideal, but it works

I like that.
Feels weirdly human.

Because It’s There

I’m probably only writing this
because it’s there.

Three years ago, I wouldn’t have started a blog.
Too much effort. Not enough time.

Now I just use it.

Helps me think.
Helps me write.
Helps me sort things out.

Not perfect.
But good enough to get started.

Without it, there’d be no Maschinenraum.

And probably no reason
to look this closely
at what’s going on
when you work with the machine.