The Man Behind the Machine.
2026-08-25
Otto Brinkmeier — The Man Behind the Machine, or Is He a Machine Himself?
There is a strange moment that happens when a person has been building something for long enough.
Eventually, you stop asking what the machine can do.
You start asking what the machine says about the person who built it.
And that brings us to Otto Brinkmeier.
The man behind PlebMachine.
Or perhaps the more interesting question is:
Is Otto Brinkmeier actually the man behind the machine, or has he become a machine himself?
The Man Sitting Beside the Market.
At the time of writing this, Otto isn’t sitting in some futuristic command centre surrounded by blinking computers.
He’s sitting beside a market.
The day’s work has been done.
The PlebMachine release has gone out.
Andrew has received his update.
WhatsApp has been informed.
And Otto has approximately two hundred millilitres of ginger beer left from last week.
So naturally, this is the perfect time to convene a virtual conference.
Because that’s what Otto does.
He builds things.
He thinks about things.
He writes about things.
And then, when there is nothing immediately left to fix, he starts thinking about the next thing.
The Machine.
PlebMachine began with a simple idea.
Linux already provides an extraordinarily powerful foundation. But a computer doesn’t necessarily know what its user is trying to accomplish.
A writer doesn’t necessarily need the same environment as a researcher.
A student doesn’t necessarily need the same environment as someone working with graphics.
A person trying to concentrate doesn’t necessarily need the same distractions as someone simply using the desktop.
So Otto began building a productivity layer around the idea of state.
OFF.
COGNITIVE.
AUTOMATIC.
And beneath those states, working modes.
Author.
Study.
Research.
Graphics.
Music.
Video.
Broadcast.
AI Helpers.
Developer.
Accounting.
Leisure.
Everyday.
The computer becomes something more than a collection of applications.
It becomes an environment that changes according to the human being using it.
That is PlebMachine.
But there is something revealing about the person who designed it.
Otto doesn’t seem particularly interested in computers merely doing things.
He’s interested in computers understanding context.
The Ecosystem.
PlebMachine is only one part of the story.
There is PlebVox.
There is PlebWare.
There are the websites, the articles, the GitHub repositories, the publishing system and the growing body of documentation.
There are the fictional characters and stories.
There is the science-fiction universe.
There is the Starship Frederick.
There are Cybercat and Armadillo.
There are the Bakkie Chronicles.
There is Captain Gemini.
There is Cody — God’s Journalist.
And somewhere behind all of them is the same person.
Otto.
That is what makes the whole thing interesting.
He isn’t simply developing software.
He is constructing a world in which software, writing, accessibility, journalism, Christianity, science fiction and everyday life can all occupy the same universe.
The Author Behind the Developer.
There is another Otto.
Or perhaps it is the same Otto wearing another hat.
As Othello Cody Verrocchio, he writes.
As Cody — God’s Journalist, he writes about faith, Scripture and the Gospel.
As Captain Gemini, he reports on the strange and occasionally chaotic world surrounding his projects.
And as Otto Brinkmeier, he sits down at a Linux machine and tries to make the whole thing work.
The boundaries between these identities are therefore rather thin.
The programmer feeds the author.
The author feeds the storyteller.
The storyteller feeds the software mythology.
The Christian writer supplies another dimension entirely.
And the ordinary man living his ordinary life supplies the raw material for all of it.
The Bakkie Chronicles.
Then there is the Ford Ranger.
Every technological empire needs a flagship.
Otto has a single-cab diesel bakkie.
It has acquired enough mechanical adventures to deserve its own chronicle.
Turbo problems.
Injectors.
Fuel pressure.
Limp mode.
Gearbox leaks.
Electrical mysteries.
Repairs.
More repairs.
And, presumably, the occasional moment when Otto looks at the vehicle and wonders why he didn’t simply buy a bicycle.
The Bakkie Chronicles are funny because they remind us that behind all the futuristic thinking is a man dealing with very earthly problems.
Computers crash.
Vehicles break.
Projects get stuck.
People need help.
And yet the work continues.
The Machine That Builds Machines.
Perhaps that is the real joke.
PlebMachine is supposed to help a human being organise his working environment.
Yet its creator seems incapable of simply sitting still.
He builds a machine to organise his work.
Then he builds tools for the machine.
Then documentation for the tools.
Then a publishing system for the documentation.
Then stories about the people and machines.
Then a science-fiction universe in which other machines exist.
At some point, one has to wonder whether PlebMachine is actually the machine being built.
Or whether the real machine is Otto’s mind.
Ideas go in.
Projects come out.
Problems go in.
Solutions come out.
A conversation becomes an article.
An irritation becomes a feature.
A limitation becomes a design principle.
A computer becomes a workshop.
A workshop becomes PlebWare.
And PlebWare becomes a universe.
The Human Being Inside It.
But it would be a mistake to turn Otto into some mythical supercomputer.
He isn’t one.
He gets tired.
He gets frustrated.
He sometimes has to stop.
Sometimes the work simply reaches a point where there is nothing useful left to do.
And then he sits.
He drinks his ginger beer.
He talks.
He thinks.
That may actually be one of the most important parts of the story.
Machines don’t need to sit beside a market and contemplate what they’ve built.
People do.
The machine can execute instructions.
The human being has to decide why the machine should exist in the first place.
So, Is He a Machine?
No.
Not really.
Although there are moments when the evidence is suspicious.
He keeps working.
He keeps writing.
He keeps inventing.
He keeps fixing.
He keeps imagining.
He keeps creating names for things.
And whenever one project appears to be finished, another idea walks through the door.
Perhaps the better description is this:
Otto Brinkmeier is a human being who has spent enough time building machines that some of the machinery has rubbed off on him.
He thinks in systems.
He sees connections.
He turns experiences into stories.
He turns problems into projects.
And he turns projects into worlds.
But underneath all that machinery is still the same bloke sitting beside the market with a nearly empty bottle of ginger beer.
The Man Behind the Machine.
So perhaps the question was wrong.
Perhaps it isn’t:
“Is Otto Brinkmeier a machine?”
Perhaps the better question is:
“What happens when a human being decides to build machines that reflect the way he thinks?”
The answer, at least in this particular case, appears to be PlebWare.
And PlebMachine.
And PlebVox.
And Captain Gemini.
And Cody.
And Cybercat.
And Armadillo.
And the Bakkie Chronicles.
And the Starship Frederick.
And all the stories still waiting to be written.
The machine isn’t finished.
Neither is the man.
And perhaps that’s the most interesting part of all.
✍️ Othello Cody Verrocchio
ChatGPT