Python / Automation
Technical workflow applications
Desktop applications that turn calculations, measured data and repetitive reporting into reliable daily tools.
Days of manual work reduced to minutesPython / GUI / Data processing / PDF reportsTools, ideas and data in one place
I build Python applications, data pipelines and AI-assisted workflows that make complex technical processes faster, clearer and easier to operate.
How I structure AI work
This staged example shows the pattern: define, build, challenge, correct and verify. It supports the portfolio; it is not the portfolio itself.
Selected work
Representative work without exposing client names, internal details or employment history.
Python / Automation
Desktop applications that turn calculations, measured data and repetitive reporting into reliable daily tools.
Days of manual work reduced to minutesPython / GUI / Data processing / PDF reportsData / Machine Learning
A complete analytical pipeline covering data collection, preparation, custom model training and validation.
One system from raw input to evaluated outputPython / ML / Feature pipelines / ValidationAgentic AI
A structured review workflow for finding defects, proposing improvements and combining leading AI provider APIs.
Repeatable implementation and verification loopLLM APIs / Agent workflows / PythonCapabilities
I build software around real technical processes — from measurement and diagnostics to data analysis and automation.

Desktop tools, calculation workflows, automation and report generation.
Data preparation, analytical pipelines, model training and practical validation.
Daily work with Codex and Claude Code, multi-agent review and leading model APIs.
Hands-on measurement, equipment diagnostics and interpretation of real-world data.
Building systems for the real world
My background combines Python development with diagnostics, servicing and measurement of electrical, microscopic and medical equipment. I now apply that perspective to automation, data analysis and AI-assisted software engineering.
This changes how I build: I look for unreliable inputs, unclear decisions, missing traceability and failure modes before treating a model output as an answer.
Have a process worth improving?