Financial services and data operations
Working close to operational data exposed the cost of manual handoffs, unclear status, and processes that depended on individual memory.
About · The path here
I moved from operating workflows to building them.
My work started in financial services and data operations. Repetitive processes made one thing clear: as the volume and complexity grew, automation stopped being a convenience and became part of doing the job responsibly.
How it developed
Curiosity became a way of working.
I wanted to understand not only what a process produced, but how the whole system behaved and where it could fail.
Could the system do more of the work?
Python and automation offered a practical answer. The focus shifted from completing repetitive steps to designing workflows that were faster, more consistent, and easier to inspect.
Data engineering and observability
Automation is only useful when its outputs can be trusted. That led to a deeper interest in data quality, monitoring, maintainability, and the operational life of a system.
Learning infrastructure from first principles
A Raspberry Pi experiment became a homelab. Running Docker, networking, monitoring, DNS, and home automation made abstract infrastructure lessons immediate and personal.
What matters
Useful, observable, maintainable.
A system is only valuable if people can trust it. I prefer solutions that are easy to debug and understandable by the next person who inherits them.
Outside work
Different ways to measure progress.
Photography encourages attention. Travel changes scale. Running makes improvement tangible. Personal projects create room to follow questions that do not yet have a business case.