From Schematic to Dashboard — 35+ years turning ideas into working hardware and software, one clean build at a time.
I've been building things — first with a soldering iron, then with code — for over 35 years. My path started in IC layout and custom PCB design, and over the decades it grew to include embedded firmware (PIC Assembly, C), full-stack web development (Python, Perl, PHP), and everything in between. I call myself a "whole-stack" engineer, because the line between hardware and software has never felt like a real boundary to me — just different tools for solving the same kinds of problems.
Early in my career, I worked on prosthetics R&D at Sabolich, which led to two U.S. patents. I've also worked at National Semiconductor, Parallax Inc., Oklahoma Robotics, and Codex Energy, building everything from IC-level designs to a 1,000+ node industrial communication network. Since going independent, I've kept that same range — recent projects include a 96-channel servo control hub for a robotics client, a cloud-connected clock that renders patterns from a server in real time, and a full inventory/request-tracking web application built from scratch.
Outside of client work, I write for Nuts and Volts magazine, run a YouTube channel (@ICPolyman) where I document real projects as they happen, and I'm currently working on a book, Fundamental Flow, paired with a companion web app I built called "Wired to Think" — a visual flowchart builder that compiles directly into working firmware.
I was also an early founder in the Oklahoma City maker and hackerspace scene — OhmSpace, and later Prototek — and I've stayed close to that community for decades. If you've been around OKC hardware circles long enough, there's a decent chance our paths have crossed before.
What I bring to a project isn't just technical skill — it's the instinct that comes from having built hundreds of things across every layer of a system, so I can usually tell early on where a design is going to cause trouble, and fix it before it does. I like clean, well-documented work that still makes sense to someone else six months later — including future-me.
Full project archive: weathersiren.com/Portfolio/
Live examples: weathersiren.com (weather app), weathersiren.com/Express/about.html (inventory system), weathersiren.com/Connect/ (skill-matching tool)
Resume: weathersiren.com/resume.pdf
Work Terms
Hours: Flexible — I typically work core hours during the week but can adjust for project deadlines or client time zones. I'm responsive and will let you know upfront if a request needs more lead time.
Payment: I work primarily hourly. It's the fairest structure for both sides — you only pay for work actually done, and it keeps scope honest, since I've had fixed-milestone projects drift through feature creep in the past. I track and report time clearly so you always know where the hours are going. Fixed-project pricing is possible for very tightly scoped work, but hourly is my default and strong preference.
Communication: I keep clients updated proactively rather than waiting to be asked — you'll know where things stand without having to check in. I document as I go, so you're never left with undocumented work or a black box at handoff. Email or messaging through the platform both work well; happy to hop on a call for anything that's easier to talk through than type out.
Scope: I'm comfortable with narrowly defined tasks (a single firmware fix, one PCB revision) as well as full end-to-end project ownership. If a project's scope shifts mid-way, I'll flag it and discuss adjusted terms before continuing rather than letting it creep silently.