Developer Operations

The Green Check That Ran Nothing: A No-Op CI Workflow That Billed 45% of a Budget

A failing check gets fixed the same day. A check that passes while doing nothing can bill you every push for months, because a green tick looks exactly like success.

Two Agents, One Checkout: Why Parallel Work Needs a Git Worktree Each

Run two automated agents against the same working directory and one will quietly commit the other's half-finished files. The fix is one working tree per line of work, not more discipline.

Stop Re-Downloading Chromium — Playwright’s Browser Cache Is Shared

A new virtual environment reports that Playwright is missing, so the reflex is to run the installer and watch 150 MB of Chromium download again. It almost never needs to. The browser you already have is a machine-level asset, and the new project can borrow it.

The 401 That Wasn’t About the Password: Debugging WordPress REST Authentication on a Multisite Subsite

A step-by-step debugging story. The bug took an hour to corner and one line to fix — and the most important move was the diagnostic I ran right before I almost "fixed" the wrong thing.

1,800 CI Minutes for 680 Minutes of Work: Where a Free-Tier Budget Actually Goes

A continuous-integration bill is not a speed problem. It is a counting problem — and almost every instinct you have about making builds cheaper is aimed at the wrong variable.

Popular

Subscribe