I built Yin’s Background Studio through a semi-automated conversation: AI proposed bounded changes, I ran them on a live WordPress server, and the resulting logs and screenshots determined the next move. The system eventually grew from one repeating background into classic mosaics, scattered collage, persistence, density and colour controls. Now I want to try the next workflow seriously: let an agent inspect, edit, run, see and verify the project itself.

The existing method is my evidence base, not the method…
Continue reading →

After building a multi-site WordPress backup system through a long patch-and-verify conversation, I wanted to revisit the entire process without assuming that its present form deserved to survive. Managed agents can now maintain state, operate tools inside sandboxes, enforce hooks, delegate evaluation and continue for hours. What would happen if that infrastructure were applied to the same project? Which manual loops would disappear, which controls would move into code, and where would human judgment change?

This is a comparison, not…
Continue reading →

Over several days, I built a centralized WordPress backup system by working with AI one verified change at a time. The AI wrote a great deal of Bash, Python, PHP and JavaScript, but it never independently controlled the production server. I inspected the evidence, ran each bounded operation, questioned incorrect diagnoses and decided when a procedure was finally reliable enough to automate.

This was neither ordinary manual coding nor fully agentic development

When people discuss AI-assisted programming, they often imagine…
Continue reading →

New function updated: the centralized backup dashboard can now schedule all four WordPress backups automatically. The system runs them sequentially during an off-peak UTC window, while the existing global lock remains the final authority. In other words, four websites may queue politely, but they are not allowed to charge through the VPS door together.

Automatic Sequential Backups

The original dashboard supported manual background backups for four isolated WordPress installations. That worked well, but it still required an administrator to open…
Continue reading →

I’ll update this article when GitHub supports IPv6. Idk when…

***

In 2026, an IPv6-only VPS could serve websites perfectly yet still fail at the humble task of pushing a backup to GitHub. The website was healthy; the route was not. This case study explains how I used Cloudflare WARP only for temporary IPv4 egress, deliberately kept native IPv6 and SSH outside the tunnel, and made every connection self-cleaning.

A Small Qualification Before the Shocking Part

The title is intentionally…
Continue reading →

Yin’s Background Studio (as shown in the background of this website) began as a small WordPress theme enhancement for selecting one repeating background and evolved into a validated composition engine supporting static, random, weighted, persistent, reduced-motion, mosaic and scattered-collage modes. The project demonstrates how to extend a mature theme safely while preserving existing media, limiting animation costs, avoiding layout shift and making every production change recoverable.

The original problem

The website originally displayed one selected background at a time. An…
Continue reading →

Yin’s Background Studio began as a refactoring task: replace a fragile, hard-coded random background selector with a native WordPress administration surface. The finished system stores multiple media-backed backgrounds in one option, supports static and random selection modes, handles reduced-motion fallbacks, previews images and videos, and validates manual sizing on both the client and server while preserving rollback at every deployment.

Technical environment

The implementation was developed on a small, resource-constrained WordPress server. At the time of the work, the confirmed…
Continue reading →