How I Approach Technical Work

  • I start with team workshops to define the real target before any implementation starts.
  • I map the current workflow with operators, engineers, and managers to identify where work is slowing down.
  • I automate only after the process is clearly understood, so automation removes friction instead of hiding it.
  • I build custom solutions for each operational context because generic tools are often not optimized for specific constraints.
  • I connect software decisions with infrastructure, cabinet-level field conditions, and real business requirements.
  • I prefer complete and reliable delivery over partial fixes that only cover the symptom and leave the root problem unresolved.

Technical Stack

Frontend

ReactNext.jsSVG interfacesDashboard UXAdmin panels

Backend

PythonDjangoFastAPI-ready architectureSQLAlchemyAlembic

Databases

PostgreSQLPostGISSQLiteGeospatial modelsAudit history

Automation

PowerShellMicrosoft Graph-style reportingSystem checks

Infrastructure

Microsoft 365Entra IDSharePointWindows DefenderQRadarNetAlly

Field systems

CNS/BMSHVACControl cabinetsSensorsActuatorsCommissioning support

Need someone who can connect software, infrastructure, and field reality?

I build practical systems for teams that need better visibility, less manual work, and cleaner technical operations.