Pandas rarely raises an exception. It guesses, and the numbers come out wrong. Four gotchas that break a pipeline quietly: type inference on import, index alignment, copy versus view, and merges that duplicate rows.
WordPress 7.0 RC1 is out and the April 9 date is still holding. The AI work worth watching sits in the AI Experiments plugin: C2PA provenance, content classification, and the MCP adapter that lets models discover what a site can do.
WordPress 6.9.2 shipped without three of its ten security commits, then broke classic themes that return stringable objects from template_include. What happened across 6.9.3 and 6.9.4, and what the Core team is changing about the process.
ELT gave analysts more power and took away the discipline that kept SQL logic sane. What a real transformation layer needs: modular models, version control, tests, and lineage you can read before you drop a table.
A no-show model with a 0.9 AUC turned out to be reading a timestamp the database only wrote after the event. Same bug shows up in a WooCommerce hook, and the fix is building features from the data as it stood at prediction time.
WordPress 7.0 ships the PHP AI Client, and the community has already built connectors for Grok, Mistral, Ollama and OpenRouter. What each one covers, how provider registration works, and the switching case worth testing first.
Alt tags do not save a layout that falls apart at 150% zoom. Setting up Figma variable modes for 100, 120, 150 and 200 percent, seeing what breaks when you toggle them, and the rem-based CSS that keeps the scaling honest.
Core now ships a provider-agnostic PHP API for AI work. The SDK and wrapper split, the fluent builder for text and image generation, feature detection before you draw any UI, and why bundling php-ai-client yourself now fatals.
Gutenberg 22.7 puts editorial rules in the database instead of a forgotten PDF. A look at the wp_content_guideline post type, the REST endpoints, and what a persistent rule set gives an AI assistant.
Claude Code forgets everything when the session ends. The setup I use: a post-mortem command that writes to CLAUDE.md, skill files for the quirks of the stack, and a daily pass over the logs.