What I do

I take repetitive, error-prone computer work and turn it into something a machine does quietly in the background — built in small, verifiable steps.

The kind of work that fits

• Office automation — re-typing data between spreadsheets, daily aggregation, copy-paste reporting, gathering the same information every morning.
• Data & signals — anomaly detection on equipment or sensor data, simple monitoring, turning raw logs into something readable.
• Hardware ↔ software — embedded firmware, FPGA/HDL, microcontrollers, and the Python tooling that ties them together.

How I work

• Small first. We start with one concrete task, build a small prototype, and confirm it actually helps before going further. I avoid oversized systems that never get used.
• Reliability over cleverness. Twenty years of factory-floor engineering taught me that the only thing that counts is whether it keeps running tomorrow.
• Easy to hand over. When it's done, you get something you can understand, run, and adjust — not a black box that depends on me.
• Remote & async. I have a weekday engineering job, so I build and reply in the evenings and on weekends. Same-day turnaround usually isn't possible, so clear scope up front matters.

What I don't take on

Large-scale system development, same-day work, data collection that violates a site's terms of service, or automating judgment itself in regulated areas (medical, financial, legal). When something is out of scope, I'll say so early, and suggest a workable alternative if there is one.