WordPress 7.0 slipped a few weeks so the collaboration layer can sit on a custom table instead of transients. What that means for polling load, cache invalidation, and any plugin still using classic metaboxes.
The six-month version of this career change is a sales pitch. Coming from a software background it took closer to two years, and the money goes to people who can ship a RAG system that does not leak data, not to people who can write prompts.
A client ran her entire business through WhatsApp until the account was blocked on a Tuesday. What owned digital assets mean in practice, and why Brazil’s first Automattic partner writes WordPress.com into its contracts.
A colleague shipped a custom assistant in a couple of hours by wiring Google Calendar, Microsoft To Do and Notion together. Execution stopped being the bottleneck, and here is a Gemini API scheduler you can start from inside WordPress.
A decade of explaining why WordPress sites don’t feel like apps, and what 2026 changes: blocks described to an AI instead of scaffolded by hand, the Interactivity API handling state without page reloads, and theme.json holding the design system.
Drift usually means a scramble for labels and a multi-hour retraining job. This is the other route: a trainable ReflexiveLayer over a frozen backbone, label-free drift triggers, and async weight updates that never block inference. It recovered 27.8 points of accuracy and cost recall.
A contact form can be technically perfect and still lose the lead if the submission just lands in an inbox. Normalizing data in the browser, guarding against double submits, and structuring the webhook payload so a CRM can read it.
Buying every tool with an AI suffix is not a strategy. Splitting autonomous from augmented productivity, why a broken human process makes an agent hallucinate, and where the return on a 2026 AI budget actually sits.
WP Packages is a community-funded replacement for WPackagist from the Roots team. It speaks the Composer v2 metadata protocol, so a ten-plugin resolve takes 0.7 seconds instead of 12.3. Here is what changed and how to move your composer.json over.
Wrapping a model in DDP is the easy part. The rest of the pipeline is where distributed runs go wrong: process group setup, calling set_epoch on the sampler every epoch, and keeping checkpoint writes on rank 0.