Validate before expanding
An MVP should expose whether the core assumption holds—not prove how many features fit.
About Yancy
Independent developer building local-first software tools and precision measurement hardware, with real status and evidence on the page.
From coding-agent handoffs and everyday automation to small-force measurement, I build bounded products that stay lean and can be verified firsthand.
I explore developer tools, automation, data products, and real-world problems that can be tested with small prototypes. This site does not present every workspace experiment as a product; software or hardware appears only when its public scope, status, and support route are clear.
Sutie is the validation project in the public directory. It explores traceable web excerpts, clipboard history, and app-level flows without rewriting standard copy and paste.
Force Analyzer extends the same honest-status, traceable-evidence approach to hardware by presenting the sensor, acquisition unit, calibration, and desktop software as one chain while keeping component datasheet claims separate from whole-system performance.
An MVP should expose whether the core assumption holds—not prove how many features fit.
Work that can stay local should stay local; pages that do not need tracking should not carry trackers.
A development candidate, an automated test, user acceptance, deployment, and public release are distinct evidence levels.
03 / GitHub
Follow public code and future project updates.