IT leadership.
Still hands-on.

PROCESS TIMING In use · Manufacturing

Where do the hours
in a batch actually go?

A manufacturing business needed to understand the time going into each batch—not just at individual stations, but between steps, too.

I built a shared timing app that follows a batch through the process. It records station runs, keeps the targets attached to those records, and brings completed batches together in an exportable history.

The owner now uses those records to understand operator hours at each station and the time between steps, informing process costing.

That distinction matters: time spent at stations and total elapsed time answer different questions. Both are visible in the batch history.

DOCKERBACKUP + RESTORE Personal infrastructure · Evolving

If the host failed,
what would I need back?

As the home lab grew, the question stopped being just how to run another app. I also needed a way to bring back its data and configuration.

I built tooling to package selected Docker data, encrypt it, and verify an offsite copy. The companion recovery work separates preparation and validation from the decision to start restored services.

Recorded checks include encrypted round-trip and database restore checks, plus a verified remote checksum. Those checks are a starting point. They do not establish that every app has passed a full disaster-recovery test.