I bridge the gap between physical systems and artificial intelligence.

I didn't set out to become a software developer. I set out to be a damn good mechanical engineer.

For 5+ years, I've designed pumps, rotating equipment, and production systems in automotive manufacturing. The kind of engineering where tolerances are measured in thousandths of an inch and a bearing failure can shut down an entire production line.

I learned to be precise. To follow standards religiously—API 610, API 682, ASME codes. To document everything because someone's safety depends on it.

That discipline never leaves you.

But I also noticed something frustrating: engineers—myself included—spent huge chunks of our time on repetitive work. Re-running the same calculations with slightly different inputs. Digging through 500-page standards documents for one specific clause. Formatting reports that looked exactly like last month's reports.

Work that required expertise but not creativity.

I thought: There has to be a better way.

So I started small. Python scripts to automate my own calculations. Excel macros that saved hours per week. Nothing fancy—just tools that solved my problems.

But those scripts became web applications. Those applications led me to React, then Next.js, then full-stack development. And when large language models emerged, I saw immediately what they could do for engineering workflows.

I wasn't just learning to code. I was building a new skill set on top of my engineering foundation.

Today I run Leadership Legacy LLC, an agency that brings AI-powered engineering tools to companies that need them. I build custom AI agents, RAG systems, and automation workflows—all informed by real engineering experience.

I'm also developing EngineerCAD, a platform where AI doesn't replace engineers; it makes them more capable. Imagine CAD software that automatically checks your design against API standards, generates calculation reports, and flags potential failure modes—while you design.

That's the future I'm building.

The goal isn't automation for its own sake. It's giving engineers back their time for what actually matters: solving hard problems, innovating, building things that work.

I've sat at the desk doing tedious work when I could have been designing. I don't want other engineers to spend their careers that way.