About

I come from the machines, not just the code.

I've spent years designing and repairing industrial systems for automation machinery. That background is the difference between software that looks correct on paper and software that still works on a factory floor.

Industrial systems and automation

My working life started — and still lives — in industrial automation. I've spent years designing and repairing the systems that drive automation machinery, and I specialize in two things that usually live in separate departments: electrical design and software design.

Working across both means I don't hand a design over a wall. The panel, the wiring, the controls, and the code that runs them are one system, and they get designed as one system.

Retrofitting and restoration

Much of that work is bringing older equipment back to useful life. I retrofit old manufacturing equipment with modern CNC systems — taking machines that predate modern controls and giving them a modern brain, so they stay in service instead of becoming scrap. I also restore old precision equipment, where the tolerances are tight and the margin for a careless decision is close to zero.

This is patient work. It means reading a machine that was built decades before you touched it, understanding what its designers intended, and then improving it without breaking what already worked.

Automotive diagnostics

I've diagnosed several real-world systems hands-on — engines, electrical, drivetrain, hydraulics. No two of them talk the same way: each has its own characteristics, from what it reports to what a symptom actually turns out to mean. That hands-on variety is also what shaped the diagnostics tools I've designed — tools that read and interpret what a vehicle is telling you.

The variety is the point. It's what allows me to work on and design modern systems while taking real-world fitment and application into account — a design that ignores where and how it will actually run is a design that fails there.

Selected background

• Industrial automation systems. Design and repair of the systems that drive automation machinery.
• Electrical design. The hardware side — panels, wiring, controls, and how they integrate.
• Software design. The code that runs the machine, and everything around it.
• CNC retrofits. Bringing legacy manufacturing equipment up to modern numerical control.
• Precision equipment restoration. Returning old precision machines to accurate service.
• Automotive diagnostics. Hands-on diagnosis across engines, electrical, drivetrain, and hydraulics — each with its own characteristics.

Why this matters to your project

It means I understand the actual implications of a design decision from both theory and practice — unlike some engineers who don't have practical experience with real-world equipment.

A decision that looks clean on a diagram still has to survive vibration, heat, a power cut mid-cycle, a worn bearing, and an operator doing something nobody planned for. Having been on the wrong end of those surprises, I design for them from the start — in the electrical work, in the software, and in how the two talk to each other.

A design decision that looks clean on paper still has to survive the shop floor.

How that shows up in the work

Whether I'm building a website, a business tool, an AI system, or something that has to drive real hardware, the same habits apply: understand the problem properly, choose the right tool rather than the convenient one, and build it so it keeps working when conditions aren't ideal.

That is what "reliable, resourceful, and dependable software that works for you" means in practice — and it's the standard every project under this company is held to.