How I work
Software development & workflow automation
I build software for the work people actually do.
I’ve built applications around work I know firsthand. That’s where I start with software: the task someone needs to get through and the parts they keep having to do by hand. I want the application to make that work easier to carry out and easier to understand.
Walk through the task
I start by following a task from the information coming in to the result someone needs. I pay attention to repeated copying, manual comparisons, and the points where people stop to find something or ask for help.
I also look at why those steps exist. A repeated task may be ready for automation. A handoff may need a different process before software can help. Understanding the work gives me a basis for deciding what to build.
Build from problems I’ve worked through
At Audi, I built audit applications and management reporting tools, and configured a Microsoft Copilot agent to support the warranty audit process using Audi’s SPREAD AI tool. Earlier, through AiM, I built applications for an Android phone toolkit designed to help approximately 1,000 inspectors and auditors solve field problems.
In my own projects, I configure and test local language models with development assistance from Codex and Claude. I run Qwen, Gemma, and Mistral through Ollama. That gives me a practical way to try ideas and examine the results while working on the surrounding application.
Show how the result was reached
Input
I work out which information the task needs and how the application should handle missing or conflicting records.
Logic
I make the rules explicit, including what happens when a calculation or decision depends on incomplete information.
Output
The result needs enough context for someone to understand it and take the next step.
Exceptions
I keep cases that need attention visible, with a way for someone to review and resolve them.
Build for the people using it
I connect interfaces and data with the rules behind the work. I think about how someone enters information, how they check a result, and what the application needs to share with other systems.
I also think about what happens after it’s built. Someone will need to understand the logic, change a rule, or investigate an unexpected result. Those needs belong in the design from the beginning.
Show me the part that takes too long
Bring an example of the task as you do it today, including the information you start with and the result you need. Show me where you repeat yourself or have to work around a limitation. We can work out what the software needs to do from there.