Profile

I go deep on fundamentals rather than recipes. I want to know why something works — because that's the layer where the interesting problems live.

Method

I look for the small repetitive things everyone tolerates — then engineer them out.

That instinct is what most of my projects come from. A friction point in daily life, a possibility nobody bothered to chase, and then a working prototype: a Python service, a KiCad board, a printed enclosure, a data pipeline that quietly does the job forever.

Principles

1. 01
   Find the friction

   The best projects start as an annoyance, not a spec.

2. 02
   Automate the mundane

   Automation is the washing machine of modern systems. Tiny savings compound.

3. 03
   Understand the layer underneath

   "It just works" is where the question starts, not where it ends.

4. 04
   Useful beats clever

   What engineers like isn't always what people need.

Working with

• Python
• Django
• pytest
• C / C++ embedded
• KiCad
• Fusion 360
• Linux · Docker · Nginx
• Claude Code

This site

RAE — Runnan Automated Environment — is the platform those numbers come from. It collects from solar inverters, network storage, and 3D printers on a few seconds' cadence, then turns the result into something worth looking at. It's a living workspace: some of it is finished, much of it is evolving, and a few corners are intentionally rough, because that's how building actually works.

If you like systems that do real work and prototypes that escape the lab, you'll feel at home here.