Background & approach
Understand the work. Make it easier.
I like building things that solve practical problems for businesses: less copying between systems, fewer repetitive steps, and information that's easier to use.
What interests me
The small tasks that add up.
A task doesn't have to be complicated to take up a lot of time. Moving information from one tool to another can become a daily chore when the systems don't connect.
For a painting company, I automated data extraction from Workyard into Google Sheets. It saved up to 30 minutes a day in manual data entry. The useful part was connecting the tools the business already used.
That practical payoff guides how I think about software. I want to understand what people need to get done, find a change that helps, and build something that fits their working day.
How I work through a problem.
Understand the routine. Find out how the task gets done, which tools are involved, and where the time goes.
Build the useful connection. Automate a repetitive step, move information between systems, or make an existing process easier to follow.
Keep it practical. Judge the change by what it does for the business and the people who use it.