Who merges so late, past midnight's chime, still pushing bugs to master's line?
The runtime existence check that kept one index rewrite safe to deploy in either order was a one-off. Here’s the same pattern turned into a reusable pre-deploy CI gate for a whole network.
A shared plugin version bump, a branch-validation step, a version-skew incident, five index migrations across a network, and a documented PR — run as one supervised agent loop instead of six separate manual steps.
An index that fixes one site’s slow query has a write cost paid by every site sharing that database tier. A checklist for deciding whether a covering index actually pays for itself, before adding it.
A shared plugin update needed five new indexes across a multisite network. The bug that almost shipped wasn’t in the indexes — it was in assuming a diff between two versions was the same thing as the full version.
The SAVEQUERIES mu-plugin from the last post left you with a raw log file and a promise to wrap WP-CLI commands around it. Here’s the tool, not just the promise.
An N+1 query pattern and a pagination batch-size mismatch, both inside a popular SEO plugin’s sitemap code — fixed by swapping internal objects at runtime, not by maintaining a fork.
A hardcoded USE INDEX hint deep inside Yoast SEO core was sorting tens of thousands of rows the slow way. Here’s how to find a bug like that, fix it without forking the plugin, and ship the fix safely.
Production slow-query logs only show what happened to run during their capture window. Here’s how to find what they miss — and a measurement mistake that almost shipped a bad fix.