Tools
13 utilitiesPersonal R&D Lab
These are tools I built for myself — and kept improving.
Every utility here started as a personal frustration. Over the years I wrote the early versions in raw code — mostly to solve my own workflow problems as a CIO building systems, writing documentation, formatting LinkedIn posts, and testing infrastructure ideas. What you see now is the result of iterating on those originals using AI-assisted coding tools, and more recently with vibe coding — where I can describe what I want and the code builds itself.
This isn't a product. There's no roadmap, no pricing, no team. It's a running log of what I've built, used, broken, and rebuilt. I'm sharing it here because a few people asked, and because it's more interesting to build in public than in private.
If something is useful — great. If something is broken or could be better — I genuinely want to know. These exist for fun and for feedback.
Personal use firstBuilt with traditional codeUpgraded with AI toolsVibe coded iterationsOpen for feedback
Development History
How these tools actually got built
From raw utility scripts written out of personal frustration, through framework refactors and AI-assisted iterations, to a running R&D experiment in spatial UI design. Here is the honest timeline.
2008 – 2016
The Raw Code Era
Scratching my own itch with a text editor and patience
Everything started as a frustration. I was a CIO managing infrastructure, building systems, writing documentation — and kept running into the same micro-problems. No good tool to format a JSON blob. No fast way to diff two config files. No clean markdown preview that ran in the browser. So I built them. Raw JavaScript, a bit of CSS, saved locally. Nothing to look at. Everything functional. These weren't projects. They were power tools I made so I could stop losing time to things computers should handle.
Vanilla JSZero dependenciesUtility-firstBrowser-native
1 / 5