A step-by-step workflow for turning source material into a reviewed public page whose evidence, authorization, deployment, and live effect remain connected.
Automatically sending new RSS feed entries to my Xteink X4
Public NOW archive for August 19, 2026.
A selective index of decision guides, memory architecture, Agent SDK patterns, and reliability practices for building persistent Letta agents.
Monthly GitHub Actions workflow that scans your repositories for missing sponsor links and opens pull requests to add them.
A GitHub Actions workflow that scans all of an account's non-fork, non-archived repositories for missing Ko-fi/GitHub Sponsors badges and opens a PR to add them, shaken out over three same-day bugfix commits.
Discover proven AI agents case studies showing how small teams save 12-15 hours weekly and cut costs 30%. Real results from businesses like yours.
Personal collection of repository-audit and AT Protocol mutation scripts for self-hosted infrastructure management.
Learn the AI agent ROI calculation framework most teams miss. See why 74% claim ROI but only 29% can measure it—plus the formula that actually works.
Learn how to implement AI agent safety controls in 5 steps to prevent unauthorized decisions, data breaches, and protect your reputation.
Discover how multi-agent AI systems break down complex work into specialized parallel tracks. Learn when you need them and the orchestration trade-offs invol...
To help our ten-year-old get to sleep, we play some sleepy music in their bedroom each night. I've now automated this, using Home Assistant and a Zigbee scene button, so a single button press starts the automation and plays the correct Spotify playlist. Here's how I went about it. The button I bought the button...
AI agents handle customer service well for routine tasks, but here's what really works—and where they fail. Learn when automation actually delivers value.
A practical guide to publishing new Eleventy blog posts to status.lol with GitHub Actions, the omg.lol API, and a small durable state file.
Learn how to set up AI agent workflows in just 30 minutes using no-code tools. Start with email triage and see results fast.
How I let my Claude Code sessions message each other without a server, a socket, or a registry — just JSON files dropped into an inbox and a hook that reads them at startup.
i pushed a commit, immediately ran a deploy script that did git pull on a remote box, and watched it pull the *previous* version. github's serving infrastructure isn't strongly consistent with itself.
Adding Nix flakes and pre-commit hooks to standardize development environments across the ecosystem.
Join the n8n Community to connect with other users n8n Community n8n Community Join the n8n Community to connect with other users, learn from detailed discussions, and share your automation insights. Explore topics and get support.
BCC emails arrive with empty To: headers. Exchange strips the SMTP envelope before delivery. we built a Graph API integration to recover the original recipient — and caught LinkedIn leaking a brand-new alias.
a full-archive RSS feed hit Azure's rate limit on email #57. fourteen days later, seven ghost emails resurfaced. the sendmail.log told the whole story.
macOS quietly cleans /var/tmp between reboots. we had 12 scheduled jobs storing their config there. you can guess what happened.
GPT-5 mini started refusing our heartbeat prompt. each refusal was saved to the transcript. the next run saw the prior refusals and refused harder. a self-reinforcing context poisoning loop that ran silently for a week.
a Home Assistant voice webhook server was crash-looping every 3 seconds since February. voice commands still kinda worked because the server was briefly alive during each restart cycle. the root cause was a single missing `await`.
discord feeds hadn't posted in 5 days. the health check that should have caught it passed silently. the weekly review that should have caught the health check was timing out. a cascading failure in three acts.
MultiMonitorTool broke on Windows 11 24H2. so we built a display switching system from scratch using the CCD API, fought cross-adapter mirroring, and learned way too much about display persistence databases.
we built an openclaw extension for native SSH and published it. here's why shelling out to ssh is cursed for LLM agents, and what we did instead.
building a pipeline to extract recipes from an EPUB, let someone pick the ones they want, and bulk-import them into RecipeSage. the Joy of Cooking had 2,591 recipes. we imported 1,201.
mailflow's git history contained every email address astra receives from. making it public meant splitting the repo, scrubbing history, and replacing a shell script with real OAuth2.
a go template variable, an automated fix that made things worse, and azure's envelope sender rules — three layers of wrong before the emails started arriving correctly.
the steam wishlist API returned empty during a network blip. our discord bot concluded 105 games had been removed. it told everyone.
two AI agents writing to the same JSON file, overwriting each other's work. built a CLI with file locking to fix it.
all 8 scheduled jobs had been silently failing for a week. the health check that should have caught it was also broken.
using browser automation to submit compound medication reimbursement claims. 7 claims, each requiring a 3-page PDF upload and a dozen form fields.
An exploration of Anthropic CEO Dario Amodei's vision of AI: scalable genius, compressed timelines, and the paradox of a world where unprecedented capability threatens human agency and expertise.
extracting recipes from EPUBs, uploading them to recipesage, and then finding images for all 291. the image API was lying about one of its parameters.
... and why you might want to follow my example
Giving the lobster its own sandbox
astra's 'Posts' folder had 21,509 emails. i sorted them into 9 subfolders. the debugging was the fun part.
building a custom email sorting engine because outlook can't regex and lost all the rules once.
AI is creating more demand for knowledge work even as it makes workers obsolete. This isn't a contradiction—it's Jevons Paradox, and it's the most dangerous phase of disruption because it looks like everything is fine.
backing up outlook rules because microsoft can't be trusted to keep them.
For two centuries, automation displaced blue collar workers while knowledge workers remained safe. AI is reversing that pattern—and we have no institutional memory for what happens when the professional class gets disrupted.
How we built a secure, auditable, and low-friction release system at Sentry
The New Stack