Notes from WordCamp Asia 2026 in Mumbai: plugins and themes landed on every paid WordPress.com plan, the speed build put AI against raw FSE work, and Nirav Mehta’s session covered where LLMs still break. Here is what held up as useful for real builds.
WooCommerce ran a bug blitz: support engineers, not the core team, shipped more than 170 fixes across 20-plus products in a few weeks, helped along by Claude Code and a purpose-built dev environment skill. Here is how that workflow held together.
Overnight batch syncs stop working the moment an AI feature depends on the data. Five steps toward a real-time data pipeline: pick the high-impact flows first, read the binlog with change data capture, and keep the old job running until the numbers agree.
HealthPress.io runs clinic programs in Malta, hospitals in Dubai and a certification course reaching 60 countries on one consolidated WordPress.com setup. A look at why Bela Grundmann stopped managing servers, and what breaks when you don’t.
Hiring for hyper-depth became the default advice for WordPress teams, and it makes messy stacks harder to fix. My case for range, what generalists catch that specialists walk past, and how much of the specialist layer AI already covers.
Notes from the latest WordPress AI contributor meeting: the MCP client is becoming a normal plugin instead of a Composer package, the Abilities API is getting real exception handling, and AI agents are getting a proper block dictionary.
The experimental core dev toolkit is a desktop app built on Playground and WASM. It bundles Git, Node and npm, so a contributor can clone wordpress-develop and generate a Trac patch without installing anything first.
How I pull OpenStreetMap data into Power BI: an Overpass QL query that returns filtered CSV, wired up through the Advanced web connector and plotted on Azure Maps. No GeoJSON middleware, no paid connector.
In a 200-task benchmark, nearly 91% of ReAct agent retries were spent on errors that could never succeed. The three fixes I use: an error taxonomy, per-tool circuit breakers, and tool routing that stays in code.
Why analytics reports come back slow and wrong, and why the fix is structural: the three modeling stages, the move from write-optimized OLTP like WooCommerce to read-optimized OLAP, the star schema, and SCD Type 2.