IT Architecture
Server, network, cloud and hybrid architecture designed for failure and evolution.
← Back to home01 PROFESSIONAL PROFILE
I design systems end to end — from the problem to operations.
I work across business processes, architecture, software, infrastructure and operations. The goal is to connect these layers into a manageable system and carry it through to production.
02 / EXPERTISE
Areas of responsibility
Software Engineering
Web, Desktop, Mobile, API and specialised industry applications.
Infrastructure / Production
Linux, Proxmox, Docker, PostgreSQL, monitoring, backup, updates and rollback.
1C Enterprise Systems
1C servers on Linux/PostgreSQL, workstations, support and diagnostics.
Security Architecture
Segmentation, controlled access, audit, least privilege and recovery.
GIS / Spatial Systems
Spatial data, offline-first, synchronisation and industry GIS workflows.
Business Processes
Finding manual work, integrating systems and designing target workflows.
03 / ENGINEERING PRINCIPLES
Principles you can use to evaluate my work
System before technology
The stack comes after the process, data, constraints and success criteria are understood.
Production is designed upfront
Monitoring, backup, updates and recovery belong in the architecture before the first release.
Change must be reversible
An update has acceptance criteria, a return point and a controlled rollback path.
State must be observable
Logs, health checks and diagnostics keep decisions grounded in evidence rather than assumptions.
04 / END-TO-END
What I can own end to end
Process and requirements analysis
Target model and component boundaries
Software and integrations
Deployment, security and operations
Updates, analysis and further development
05 / PUBLIC WORK
Public evidence of the approach
Case studies show the problem, architecture, responsibility and operational outcome rather than a technology list. Engineering Notes capture principles that repeat across real systems.