Generating AI answer…
From Private to Public: A Practical Guide to Migrating Your GitHu...
My GitHub Pages deployment just broke, and the reason is exactly what I suspected: my paid...
Escaping GitHub Pages: The Quest for Raw Log Files and Deeper SEO...
I’m drawing a line from the basic idea of sequenced actions, like a Turing machine or even...
I Don’t Know What to Do Sometimes | Mike Levin SEO AI Education
While I missed some chances, I still love coding, writing, and experimenting with tools li...
The Logistics of Thought: From S-Curves to the Command Line | Mik...
I started by thinking about a simple metric like GitHub activity and spiraled into backup...
My GitHub Pages deployment just broke, and the reason is exactly what I suspected: my paid plan lapsed. This isn’t just a bug; it’s a philosophical fork in the road.
I’m drawing a line from the basic idea of sequenced actions, like a Turing machine or even wax-on/wax-off, to my current need for deeper website insights than GitHub Pages provides.
While I missed some chances, I still love coding, writing, and experimenting with tools like NixOS and GitHub Pages.
I started by thinking about a simple metric like GitHub activity and spiraled into backup strategies, vendor lock-in, and the mental models, like the logistics curve, that help bring clarity in this noisy, AI-driven world
It details the journey from GitHub Pages to self-hosting web logs, streaming them live, and building an an AI-powered ‘Honeybot’ for real-time analysis.
assistants, particularly within the popular VSCode ecosystem, I commissioned research to clarify the key distinction between full IDE forks (like Cursor, Windsurf, Trae) and integrated plugins/extensions (like Cline, Augment, GitHub
While I’m a longtime Vim user who values its timelessness, the sheer difficulty of editing recorded macros in VimScript finally pushed me to NeoVim; I initially switched to try GitHub CoPilot (which I disliked in Vim) but
In this article, I’m sharing how we addressed the constant frustrations of maintaining stable development environments for our Jekyll sites. We kept running into problems with Ruby dependencies, particularly native extensions causing build failures due to library mismatches or version conflicts, making it difficult to work across multiple projects. We found a robust solution using Nix flakes to define a reproducible, isolated environment that explicitly manages system libraries, configures gem b
This final article captures the essence of integrating introspective practices with cutting-edge AI orchestration to create a robust, self-validating development workflow. It synthesizes previous discussions on deterministic environments and modular project structures, delivering a compelling narrative on how to maintain human agency and critical thinking amidst powerful, yet potentially complacent, AI tools. The ‘Exosymbiotic Dialectic Workflow’ stands as a foundational concept for the ‘Future-
I am moving away from the “Second System Effect” by anchoring development in real-time utility. This entry highlights my transition to global system controls and my philosophy on “agentic negotiation”—where AI is restricted by human-placed sentinels to ensure code integrity in monolithic files like server.py. This is an important way to maintain codebase sanity as the machine begins to assist in its own evolution.