For engineers who care about system boundaries, device abstractions, architecture tradeoffs, and software delivery once the demo is over. The happy path is where demos live. Production lives everywhere else.
I am currently a Member of the Technical Staff at Panasonic Avionics. Most of the writing here comes from building connected systems, automation tools, and small pieces of infrastructure that other people eventually depend on.
Start here
Build IoT systems like software systems
Start with architecture boundaries for devices, gateways, messaging, and edge runtimes.
Read the IoT and edge systems guideMake software projects predictable
Use cases, task slicing, testing, review, and release habits keep work from drifting.
Read the software development guideSee the reference implementations
Look at working systems where the architecture has to answer to code and hardware.
Browse the project indexRecent writing
- Software is Hard /software/ 2026-05-22
- Organizing Software Projects with Kanban /software/ 2026-05-22
- Version Control Systems /software/ 2026-05-22
- Test Driven Software Development /software/ 2026-05-22
- Exposing a Go App as Claude MCP Tools /notes/ 2026-05-22
- Fixed-Point Numeric Types in Go Financial Software /software/ 2026-05-22