*My Purpose*  

I build hardware that has to work the first time. For 20+ years at Motorola and Magellan, I designed RF and GPS systems for navigation, defense, and telecom. If my design failed FCC or MIL-STD-461, products didn’t ship. If my GPS front-end had poor C/N0, drivers got lost. 

That pressure taught me: excellence is not optional in hardware. You can’t patch a bad ground plane with software. You can’t fix a 12dB desense issue with marketing. 

My purpose now is to pass that discipline to the next generation of engineers and to help teams ship clean, compliant hardware without the $80K re-spins I’ve had to prevent.

*Discipline: How I Work*  

*1. Measure First*  

I don’t guess. I bring a spectrum analyzer, near-field probes, and a VNA. Most EMI failures are visible in 10 minutes if you know where to look.

*2. Root Cause, Not Band-Aids*  

Ferrite beads are not a design strategy. When I found a DC-DC spur killing GPS at 1575.42MHz, we didn’t add shielding. We fixed the PDN and filtered the source. 12dB improvement, $2 part, no re-spin. That’s the standard.

*3. Document Like It Ships*  

Test plans, compliance matrices, layout notes. I write documentation I’d want to receive. It’s how teams learn and how products get certified.

*Goals: What I’m Building Toward*  

*Teach the Next Wave*: DFW needs RF and EMC engineers. My goal is to teach at SMU, UTA, or Dallas College so students graduate with VNA plots and pre-compliance data, not just equations.

*Raise the Bar for Small Teams*: Startups fail FCC because they can’t afford a full-time EMC expert. I do 2-hour debug calls and 1-day pre-scans so good hardware doesn’t die in a test lab.

*Keep Building*: I’m still an engineer first. Consulting keeps me sharp. Teaching keeps me honest. Both make me better at each.