About
From industrial control to products and a personal engineering platform.
I build products, modernize existing systems, and extract the parts worth reusing in the next project.
My interest is less about a particular framework and more about how systems stay understandable over time. I keep returning to the same work: separate the problem, make ownership clear, and close the gap between implementation and verification.
See the work on GitHubWorking principles
- Name the real constraint first.
- Make a small boundary and check it in code.
- Do not call an unverified state current.
Experience / journey
The current practice came from several transitions.
- 01Industrial control
A precise state had to be read before the next action.
LabVIEW · sensors · control - 02Web engineering
Physical signals became flows people could use in products.
React · Spring · backend - 03Legacy migration
Clear boundaries made old code changeable one piece at a time.
Gnuboard · MySQL · files - 04Enterprise
Parsers and process made organizational constraints visible in code.
eGov · Excel · Oracle - 05Product
Repeated problems became product and library surfaces.
PhotoGram · grid-masonry - 06Reusable systems
Runtime and control planes separated relation and ownership.
CharaWeave · Workspace Ops