I like knowing how the whole thing works.

I do not really fit into one clean category. I like software, robotics, embedded hardware, servers, and debugging systems where the actual problem is three layers away from where it first showed up.

At Clark, I work in the Laboratory for Intelligent Perceptual Systems. Most of my research has involved mobile robots, ROS, computer vision, Raspberry Pis, cameras, LiDAR, motors, and getting all of that to communicate reliably.

I also help run Lux Lab, Clark's makerspace. I maintain equipment and help students with 3D printing, laser cutting, electronics, and projects that got more complicated than expected.

Why I build things

A lot of my projects start because something annoys me. Clark's course planner was frustrating, Spotify did not organize liked music the way I wanted, and audiobook chapters sorted wrong. Those became tools.

Other projects start because I want to understand a system instead of just using it. That is how I ended up with TrueNAS, Tailscale, self-hosted CI, old thin clients running Debian, ESP32 sensors, and more computers than I need.

How I work

I ask a lot of why questions. I would rather understand why a command fixed something than save it and hope it works again later.

I also change direction quickly when something is not working. I do not mind admitting that a benchmark was bad, a design was overcomplicated, or the simple version was better.