WordPress Guidelines keeps agent memory, skills and instructions in an ordinary custom post type, and it’s headed for Core. Here’s what that means for plugins with their own memory stores, which permissions to test first, and when a separate table still makes sense.
Angle encoding costs you qubits and amplitude encoding costs you gates, and both get paid when data crosses into the system. WordPress has the same problem with autoloaded options and fat transients, and that one is cheaper to fix.
I read the WordCamp Europe 2026 schedule as a prep list. Register one Abilities API entry on staging, run the WordPress 7.0 upgrade on a copy, and pick the sessions you will actually use before Kraków or the livestream.
AWS shipped the Agent Toolkit, which gives coding agents skills, live docs and an MCP server. The part I care about is the guardrails: IAM condition keys that mark agent calls, and CloudTrail records of what the agent did. Set those up before an agent gets near a client account.
WordPress.com shipped Write, a minimal editor that still saves ordinary block posts. I compare it with distraction free mode and the Classic Editor, note what it hides from writers, and say which kind of site should get which.
A data analyst’s 12-month roadmap into data engineering reads oddly familiar if you maintain WooCommerce stores. Scheduled actions, custom order tables and cron are already small pipelines. What they lack is retries, monitoring and someone noticing when a job fails.
A beginner’s notebook ETL pipeline gets the shape right: pull, clean, save. Here’s how I’d move it into WordPress, with proper wp_remote_get error handling, a better place to load the data, and a schedule that actually runs.
A nightly job that outgrows its PHP request is a common failure on WooCommerce stores. The fix borrows the structural move from Benders’ decomposition: keep the coupling state small, split the rest into batches, and reschedule until done.
A Towards Data Science post walks data scientists through calling REST APIs from Python, which is fine in a notebook. In a WordPress plugin the same call needs wp_remote_get, error checks, a transient and a key kept out of the code. This is the version I ship.
My notes on the Lean proof assistant as a WordPress developer: what Curry-Howard, dependent types and the sorry placeholder say about writing safer PHP for WooCommerce stores, and which habits I’d copy into client code.