I learn best when there is something real to build.

01 / How I got into building things

Curiosity usually starts with “what happens if?”

I have always been more interested in how a system fits together than in treating it as a sealed box. A PC upgrade leads to thermal testing. A spare machine becomes a server. A useful script becomes a service that needs monitoring.

This site is where I keep the build notes—the useful decisions, wrong turns, and details that are easy to lose once a project finally works.

02 / What I work on

Systems that cross boundaries.

My projects move between AI agents, homelab infrastructure, embedded devices, networking, C++ software, FPGA logic, and PC hardware. The common thread is practical problem-solving: making the parts cooperate and understanding why they sometimes do not.

03 / How I approach projects

Build a small version. Measure it. Keep notes.

I prefer a working prototype with visible limitations over a perfect plan that never reaches the bench. I try to define the question, build the smallest useful system, observe how it fails, and improve the part that matters most.

04 / What I am currently learning

The space between software and hardware.

Current threads include local AI on repurposed PCs, agent operations, embedded Linux on the LicheeRV Nano, digital logic, network reliability, and making self-hosted systems easier to operate.

05 / Outside the workshop

Different ways of paying attention.

Outside computing, I enjoy diving, travel, and photography. They are hands-on in a different way: preparation matters, conditions change, and careful observation is usually more useful than rushing.