Tag: Systems Engineering

Browse our exclusive articles!

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.

Turn Windows into a Dev Workstation: One PowerShell Script

Consumer Windows is tuned for a casual user — it sleeps mid-task, phones home with telemetry, and ships gaming services a developer never touches. If you run long automation, scraping pipelines, or Playwright jobs, a few settings changes make the machine stable and quiet. Here's a single PowerShell script that applies them — and the safety steps to run it sanely.

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.

Popular

Many-to-One: Why a Mapping Backlog Outgrows Its Target Taxonomy

You're mapping a messy source vocabulary onto a clean target taxonomy. The target has about 5,600 slots, so the job must be roughly 5,600 decisions — right? The backlog is already past 8,900, and still climbing.

The Fix That Didn’t Take: When a Content-Hash Gate Skips Your Code Change

You shipped a fix to how one field is computed, re-ran the pipeline across everything, and it reported a clean run. Then the consistency check still flags those records as wrong. The fix is in the code, the rebuild "ran" — and the records never changed. Your own optimisation skipped them.

Your Dedup Scan Is Over-Counting — Because It Forgot What You Already Fixed

The report said 80 duplicate groups still to resolve. You'd been resolving them for days. You run it again after a big batch and it *still* says 80-ish. The backlog isn't stubborn — the scan is counting work you already finished.

When Your Skills Folder Is a Deploy Target, Not a Drawer

You hardened a skill in the repo, shipped the PR, and the agent kept loading the old one. Or you fixed the live skill by hand, and the versioned copy quietly stayed behind. Same root cause: the copy you run and the copy you version are two different files.

Subscribe