I got here sideways.

The manufacturing half

I started on an inspection floor in 2013 at Stanton Carpet, investigating customer claims from intake to resolution and tracing lots through SAP. The job was mostly reading records that disagreed with each other and working out which one was lying. I taught myself Power BI because building a dashboard was faster than rebuilding the same spreadsheet every Monday, and cut a credit-versus-sales report from eight hours to about two by fixing the data logic rather than the formatting.

That pattern repeated everywhere I went. At Loloi Rugs I automated the leadership dashboards, then noticed the real constraint was physical and justified a second inspection table, which raised throughput by over half. At Qcells I supported the ISO 9001 certification effort, and spent most of it making the documented procedures match what the floor actually did. At Clean Energy Associates I run pre-shipment inspections for solar module manufacturers and built the Power BI layer aggregating audit data across fifteen-plus factories.

Somewhere in there I finished a Lean Six Sigma Black Belt and the Microsoft Power BI Data Analyst certification, and a degree at the University of West Georgia.

The software half

I started building because clients near me needed websites and the quotes they were getting were absurd. That turned into Forge Development Studio: websites and AI phone receptionists for local businesses that take bookings. Fifteen client sites are live on their own domains. The receptionist answers a real phone number, holds a real conversation, and writes the job into the client's CRM.

Then I built ten arcade games and shipped them to Google Play, which taught me more about engineering than anything else I have done. Not because games are hard, but because ten apps sharing one engine across thousands of unknown Android devices is a measurement problem wearing a costume.

Why the two halves are the same job

Manufacturing quality is the discipline of not trusting a number until you have proven the instrument that produced it. Gauges drift. Sample plans measure the wrong lot. Dashboards report metrics that reset before anyone reads them.

Software has exactly the same disease and fewer antibodies. A test suite passes while measuring something adjacent to the question. A build exits zero without your change inside the artifact. A feature ships and renders behind the navigation bar, invisible to every user and every test.

I have been caught by all three. The habit that catches them is the one the factory taught me, and it is the reason I would rather show you something running in production than a screenshot of something that never was.

Outside that

I live in Calhoun, Georgia. I write and record music, and I read more standards documents than is strictly healthy.