OPERUS / WHO WRITES HERE
About me
I'm a Solution Architect with a background in software development. In my personal projects, I build software, connect devices and services around my home, and try new technologies. On Operus, I share what takes shape and what I learn along the way.

When I try a piece of software, it usually doesn't take long before questions come to mind: Why does it work this way? What is that extra step for? Could this be simpler and easier to understand?
Then I start thinking about how I would design it myself. Sometimes it remains a passing thought, sometimes I want to understand what's behind it — and occasionally it turns into a project of my own.
I'm interested in how technology and usability come together to make an application genuinely useful in everyday life. On Operus, I share my ideas, my projects and what I learn along the way to a working solution.
Curiosity came first
At eleven, I sat in front of a Commodore 16. Later, on the C64, I typed in pages of programs from computer magazines. Seeing those lines turn into something that responded to my input had me hooked.
The Amiga brought graphics, music and game worlds into the picture. I was fascinated by what people could create with limited technology — and how thoughtful engineering, design and an idea could come together to make something memorable.
That curiosity has stayed with me. I want to understand how things work, see the connections and build something of my own.
From writing software to designing systems
My career began in application development. Today, I work as a Solution Architect. My experience as a developer still shapes my perspective: an architecture needs to be practical to implement, operate and evolve.
When I work on a solution, I first want to understand the problem it actually needs to solve. Who will use it? What constraints are there? And what will a decision mean for integration, security and operations?
I enjoy moving between these perspectives. I care about the bigger picture, but I also pay attention to detail: an unclear interface between systems can cause just as much trouble as a dialog nobody understands. Good solutions need both a sound structure and care in the details.
For me, that also means explaining trade-offs clearly and questioning decisions when new information comes to light.
Personal projects keep me hands-on
These perspectives come together in my personal projects. I develop applications, connect devices and services around my home, and automate routines I encounter in everyday life.
Here, I can try new technologies and take an idea all the way through. Whatever I design, I also have to get working myself. Awkward interactions, unnecessary complexity or a fragile dependency affect me directly.
That gives me a valuable balance to conceptual work — and it's also how I unwind. I enjoy seeing individual pieces become a dependable system. Just as valuable are the experiments that show me a simpler solution is enough, or that an assumption was wrong.
New possibilities, considered choices
AI has greatly expanded what I can do as a developer. I can try ideas sooner, explore alternatives and take on projects I wouldn't previously have had time for.
I still expect to understand and check the results. Where clear rules can solve a task reliably, I use them. Where language, unstructured information or changing contexts come into play, AI can be a useful addition.
As deterministic as possible. As much AI as necessary.
I'm particularly interested in what I can run on my own hardware. When personal data is involved, I want to make a conscious choice about what goes where. I consider the benefits, the effort and the dependencies — and choose the technology to suit the task.
Why I write Operus
To me, Operus is about creating things. It's where I share what becomes of my ideas and the thinking behind them.
A finished project only shows part of the work. The questions along the way are often just as interesting: What options were there? Why did I choose one of them? What held up in practice, and what would I do differently today?
I want to share these experiences in a way others can follow. Writing helps me, too: trying to explain a decision clearly soon reveals where my own thinking still needs work.
Perhaps you'll find a solution to a similar problem here, a fresh perspective or the spark for a project of your own. And perhaps, as you read, you'll catch yourself thinking, “Surely that could work, too.” Thoughts like these often lead to something interesting.
Enjoy reading and trying things out!
Oliver