sudo clear maze
Consolidating 30+ builds scattered across tools into a single source of truth. Discovery, comparison, and maintenance workflows for scattered work.
Real builds. Real failures. Real lessons.
Where AI-generated ideas become production systems.
15 posts
Consolidating 30+ builds scattered across tools into a single source of truth. Discovery, comparison, and maintenance workflows for scattered work.
Building a cross-platform second brain on plain Markdown: Obsidian, Neovim, PARA, and the ghost folder that kept coming back.
After months in Joplin, I went looking for the needle under pressure and found out which retrieval features actually matter at 11pm.
A multi-day clipboard corruption mystery on a Wayland Ubuntu desktop, traced through five dead ends to ibus, the input method framework most users do not know is running.
Two small changes to sudomakevibe.com: a new warm light palette replacing earthy glow, and a session-scoped hint about the theme switcher.
Why the vulnerability treadmill is broken, what defense in depth actually means, and how to build systems where individual bugs don't matter.
A homelab publishing stack audit on Ubuntu 24.04 — what a routine CVE patch revealed about Node versioning and Astro version debt.
A coda to the AI-is-not-free series. The architecture is the right answer. Inaction is the more expensive failure mode.
What is actually running in my homelab — the hardware, the network, the platform, and the honest gap between what is here and what is planned.
The build log for sudomakevibe.com — stack decisions, six things that broke, and what a corrupted disk taught me about deployment pipelines.
R7 — the Carrier-Grade AI Stack. Seven layers for regulated AI deployment. Indemnity covers provenance. Insurance covers performance. Regulated AI needs both.
Part two of the AI cost series. Technical debt, false confidence, and the quiet atrophy of engineering skill. The costs that determine whether AI pays off or breaks your systems.
Everyone talks about how fast AI lets you build. Few talk about what it actually costs. Part one — the costs that show up on your invoice.
High-fidelity work requires high-fidelity documentation. Here is why this site exists as a blog and not a two-hour podcast.
Correctness, reliability, security, maintainability — these are not features. They are disciplines. AI doesn't ship them. You do.