I design, build, and deliver practical software systems. My background spans networking, aerospace, embedded systems, distributed systems, consulting, and connected products at scale.
This site is where I write down the engineering lessons that keep showing up in real projects: how small computers talk to each other, how software reaches into the physical world, and how teams can keep systems understandable after the first prototype works.
What This Site Is For
RustyEddy.com is a working notebook for practical engineering:
- IoT and edge architecture for systems that connect devices, gateways, APIs, and dashboards.
- Software delivery notes for use cases, Kanban, testing, reviews, releases, and keeping projects steerable.
- Project writeups for reference implementations and older systems with useful design lessons.
- Resume and work history for a more formal view of my background.
The common thread is pragmatic software architecture: Go, Linux, networking, embedded systems, automation, and small-team delivery.
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. That mix is why the site keeps returning to the same practical question: how do we build systems that are useful, understandable, and maintainable after they leave the bench?
IoT, Go, and the Physical World
Networking taught me how machines talk to each other. Embedded systems taught me how software meets the physical world. IoT sits directly between those two interests.
These days I build and teach practical IoT, Linux, and Go automation systems: small computers that observe, control, and coordinate with the real world. I treat IoT as a software engineering problem first: clear boundaries, stable APIs, reliable messaging, useful tests, and architecture that can evolve.
Projects like OttO, a Go-based IoT edge gateway, and RedEye, an older video and robotics system, grew out of that approach. The articles and notes on this site are the written version of that same work.
Current Work
I am currently a Member of the Technical Staff at Panasonic Avionics, working on connected systems at scale. A more formal work history is available on my resume.
I still program almost every day. I have held titles like Principal Engineer, Technical Lead, and Senior Systems Programmer, but I am most useful when I am turning unclear problems into working software, automation, and architecture that other people can reason about.
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.