About
From the glass furnace to the architecture.
I come from container-glass production and design software the way a good process is designed: traceable, irreversible where it must be, and explainable in operations.
Software engineer for industrial processes · Germany · remote and on site
I start from container-glass production: recipes, raw materials, silos, shifts, batch tickets, daily logs. These are not abstract entities. They are states that touch money, material, and safety.
That shapes how I build software. Domain bookings are not simply deleted. Calculations stay traceable. Failure paths belong in the model, not in an afterthought dialog.
For clients that means someone who understands the process first and leaves a system another engineer can explain. For employers it means ownership, not ticket throughput.
- 01
Domain first
I start from the real process, not the framework. Rules become visible, testable, and traceable.
- 02
Reliable states
Bookings, migrations, and failure paths designed so the system stays intelligible under real conditions.
- 03
Small, durable solutions
No architecture for its own sake. The smallest design that lastingly improves the process.