What I build
Clients and tools by day, servers and automation by night. The shape I keep coming back to is fixed: local first, usable offline, shipped as a single file — stay off the network if it can be avoided, skip dependencies if it can be avoided, and if a dependency is needed it still has to fit inside one exe.
The habit has a price: I rarely chase new frameworks, and a lot of things here were written the blunt way and then left alone. The benefit is that they still compile years later, and when something breaks I can read my own code and understand what I wrote.
How I work
Nothing ships that I have not verified. In the tools, every irreversible action — deleting — is off by default or backed up first; and every judgement about what something is needs two or three independent pieces of evidence before I commit to it.
In the open-source repositories the licence, the known limits and the unfinished parts are all in the first screen of the README — saying it up front is less work than explaining it after launch.
