From Heavy Steel & 350-Ton Cranes to Building Custom AI Systems: Why I Don't Build Cookie-Cutter Software

I’ll be honest: looking around the tech scene, I don’t fit the typical mold.

I cut my teeth in the roughest industrial trades out there—oil fields, shipyards, marine docks, chemical plants, paper mills, massive power plants, and oil refineries. When I was 21 back in 1988, we were out at Perdido Pass in Orange Beach driving the largest concrete pilings Alabama had ever seen. They were so massive they had to come in on barges, and it took two 350-ton friction cranes working in tandem just to pick one up off the deck.

I was young and fearless back then. Today, I’m still fearless—just not quite as young.

In heavy construction, engineers design a project on paper in an air-conditioned office. Then they send the blueprints to the field, and nine times out of ten, it doesn't work like the drawing. When you don't have the tool for the job, you don't stall out. You fabricate it right there in the dirt.

That mindset is tattooed into everything I do. When you bust your knuckles using a worn wrench that slips, you stop cussing at it after a while. You wrap the cut in a clean rag and duct tape, and you keep pulling. There is no simulation that replaces blood, sweat, and real-world failure. You only truly understand how to make a complex machine run once you understand exactly what breaks it.

About 16 years ago, I saw the tide turning and committed to mastering computers. What started as basic literacy ignited a wildfire. Today, I’m pursuing AI at university and architecting software hands-on.

I don't build cookie-cutter web apps. If someone wants something off the rack, they can go to the software equivalent of Walmart.

Through my flagship, Clear Communication Inc., I engineer custom solutions to actual, high-friction problems. I work alongside an integrated AI collaboration team—systems I architected specifically to keep continuous context, run lean backend APIs, and persist data without bloat. When a critical problem hits, I don’t sit in analysis paralysis. I move fast, build the missing piece in real time, and stress-test it under load.

I thrive under pressure. I’m the guy you call when the ship is taking on water—the one who steps on deck and figures out how to keep her afloat.

Validation to me isn't an abstract survey or a pitch deck. It’s whether the machine actually runs when you flip the switch. That's how I build, and that's why I'm here.