I’m a systems engineer. For most of my career I’ve worked on software that had to keep working: space systems, multicast routing protocols, core routers, and connected systems at aviation scale.
Now I’m focused on a newer problem. AI tools make code cheap and fast to produce. They don’t make it correct, maintainable, or safe to ship. The discipline that kept those earlier systems reliable (clear architecture, honest testing, independent review, careful releases) matters more when a team can generate ten times the code, not less.
Who This Site Is For
I write for the people accountable for delivering software at small companies: engineering managers, tech leads, technical founders, and CTOs. Your team is adopting AI tools faster than your process is adapting, and you need software that survives production, not just demos.
What you’ll find here:
- Software delivery with AI: agent instructions, verification, review, and release practices that keep AI-assisted work shippable.
- Reference projects: working systems where the architecture has to answer to real code. Trader, an FX backtesting and trading engine, is the main one, along with OttO, an IoT edge runtime.
- Engineering notes: deeper, implementation-level write-ups for engineers who want the details.
- My resume, for a more formal view of my background.
Background
I started programming on a Commodore 64 while taking mechanical engineering classes at L.A. Harbor Community College. After transferring to CSU Long Beach I switched to Computer Science, then took a job in aerospace just before graduating.
At Rockwell International’s Space Systems Division I managed Sun engineering workstations, wrote embedded and real-time software, and started graduate work at USC focused on computer networks and distributed systems.
I later joined Retix Systems, where I led a routing-protocol QA lab, then moved to USC’s Information Sciences Institute. At ISI I worked on multicast routing research and helped develop an early implementation of PIM multicast routing.
That work led to five years as a Technical Lead at Cisco Systems on the Core Routing System. The hardware was still being designed when the software work started, so the project required close attention to architecture, protocol behavior, forwarding paths, and production reliability from the beginning.
After Cisco I started Eddy Consulting, working with companies across networking, embedded systems, web systems, automation, and product development.
Current Work
I’m a Member of the Technical Staff at Panasonic Avionics, working on connected systems at scale.
On my own time I build Trader with AI coding agents, as a deliberate test of the practices I write about here: written architecture decisions, agent instructions, independent review, and CI gates that don’t care who (or what) wrote the code.
I still program almost every day. I’ve held titles like Principal Engineer, Technical Lead, and Senior Systems Programmer, but I’m most useful when I’m turning unclear problems into working software and architecture that other people can reason about.
I occasionally take on a small amount of advisory work: architecture reviews and AI-assisted delivery process for small teams. If that’s what you need, email me.
About This Website
This site is written in Markdown and built into static HTML with Hugo. It is hosted on GitHub Pages, and the source is available in this GitHub repo.