The beginning
I started four years ago with game servers for Minecraft, alongside school. What grew out of that are larger systems that develop over months, among them a platform for a sports federation, an economy system for a game server network and a language model trained from scratch.
Besides IT, I play competitive water polo, and have done since I was nine. Among other things, I placed second at the German Championship. Since summer 2026 I have been building WP Pulse, a platform for exactly this sport, in collaboration with the German Swimming Federation.
How I work
Every project starts with a conversation, preferably in person, otherwise by video call. It covers how the work is done today and where it actually gets stuck. Added to that are the conditions that are already set: existing systems, deadlines, access rights, data protection. I want that picture to be complete before I start. Every gap at this stage comes back later as a rebuild.
Out of that comes a concept with the framework of the future system. It is presented and agreed before the first line of code is written. Whatever does not fit is changed here in an hour. The same change later costs weeks.
Only then does implementation begin. It starts with the framework and grows step by step. Intermediate versions go out early, while changes are still cheap.
Client work runs through Milan Ronnenberg IT Solutions. On larger projects, specialists join the project team. I remain the point of contact.
What I offer
Consulting
A look at what is already running: infrastructure, architecture and the systems attached to it. From that comes an assessment of which technology is genuinely worth it in this case and which only creates work.
I follow new developments closely, including the ones everyone is talking about. Whether one of them actually improves a particular operation is a different question. I answer it beforehand, not once the money has been spent.
Development
The main part of my work: software built on commission, either from scratch or extended on existing systems. It ranges from the interface through the backend and security to applications that reach deep into existing processes.
How large a project becomes depends on the scope set for it. Some of it is built entirely by me. Larger work runs with a team that I coordinate. And where something has already been started internally and has outgrown what can be done on the side, I take it over and build on it.
Servers and Infrastructure
Testing does not happen on the client systems but on mine. Dedicated servers are available for that, mirroring the later production setup, in separate environments that never touch anything running live. That allows testing under realistic conditions without putting the running operation at risk, and the state of development can be demonstrated at any time.
On request I look after the servers everything runs on later in the same way: setting them up, maintaining them and keeping them running, along with the networks behind them. Before that there is often the question of where it should run at all, with a hosting provider or on dedicated server hardware.
Process Analysis
Before anything is automated, it has to be clear what actually happens. I look at the workflows, the digital ones as well as those that happen on paper or in individual people’s heads.
That shows where time is lost and which steps are worth changing. The result is a solution for this specific operation. Whatever repeats is then handled by a program.
Background
Tech Stack
A selection of technologies and tools I use regularly. Click a tile for a short explanation.