Build logs, deep dives, and TLDR takes on tech. Less "thought leadership," more real talk — including the parts that didn't work.
Build logs from projects I'm building alongside my full-time role. Grouped by project — open one to see every post in that build log. Some posts have sections behind a password; the concepts stay open, the implementation detail doesn't.
One console to fly drones, drive ground robots, sail boats, and dive underwater vehicles. Multi-domain from day one, license-clean, works air-gapped. TypeScript, Electron, MapLibre. Apache-2.0, my own IP.
I'd marked the command pipeline "designed, not wired" and said so plainly. This post closes that gap — every command now traverses RBAC → Safety → ROE → Authorization before anything moves. The architecture that made it a small change instead of a rewrite.
A multi-agent platform that turns a prompt into generated code, tests, design, and an audit trail. An append-only debugging journal — honest about what broke, and specific about why.
Two problems six weeks apart that turned out to be the same problem. A cancel button that stopped the UI but not the work. A search that confidently returned a table-of-contents fragment. Both fixed by refusing to make the primary mechanism smarter.
Local-first RAG that unifies enterprise knowledge across trackers, wikis, and code hosts — surfaces the conflicts between them, and helps a human decide with an audit trail. Read-only by design.
Some days you ship code. Some days you ship clarity. An audit found six unused dependencies, four frameworks in the docs the code never imported, and nine capabilities pitched but tracked nowhere. No features today — just a project that knows what it is.
More posts coming — build logs, TLDR tech takes, and whatever else catches my attention.
Ate mo na naman may opinion. (your big sister has opinions again.)