Focus areas
Where the domain meets the code.
These are the areas I work in. They start from twenty years inside precision manufacturing — maintenance, calibration, technical customer support — and end in the software that supports exactly that work. Not a catalogue of services: a description of what I actually know and have built.
Area 01
Maintenance and asset management — from the inside
Twenty years on the shop floor of precision manufacturing: preventive and predictive maintenance, asset hierarchies, calibration, and the reporting that keeps a plant running. I know the work the software is meant to support because I did it.
- Preventive and predictive maintenance as a daily routine, not a slide
- Asset hierarchies, maintenance schedules, and calibration cycles
- SAP key user for a plant rollout, including the requirements specification
- Manufacturer training in preventive maintenance (ARBURG, 2015)
- Twelve years of technical customer support and complaint handling across 35+ countries
Area 02
Full-stack applications for operations
Typed back ends and fast front ends for the kind of application that schedules work, tracks assets, and notifies people — the ProAct stack, built end to end.
- Python, FastAPI, and SQLModel with explicit service-layer boundaries
- React and TypeScript (strict), Tailwind/DaisyUI, Vite
- Recurring scheduling, hierarchical data models, email notifications
- Bilingual DE/EN from the data model up
- 285 automated tests (232 pytest, 53 Vitest)
Area 03
Operation and delivery
Docker, CI/CD, and reproducible environments — the work that keeps a maintenance application running inside a customer network, not just on a developer’s laptop.
- Multi-stage single-image Docker builds, running non-root
- Deployment via Git and GitHub Actions
- Test environments that mirror production, with a technical write-lock against the live system
- Reproducible builds — the same artifact from commit to server
Area 04
Secure, auditable systems
Access control, signed action links, and audit trails designed in from the start — because a system that touches maintenance records has to be trustworthy and traceable.
- Role-based access control, invite-only accounts, JWT and bcrypt
- HMAC-signed one-click links (complete or postpone without a login)
- Audit log, soft-delete with a recycle bin, rate limiting
- Strong typing and explicit error boundaries over silent fallbacks
The work sample
ProAct puts these together.
ProAct is where the maintenance domain, the full-stack build, the delivery, and the security work meet in one application — built solo in four weeks.
See ProAct