Todd Wardzinski of the Red Hat team makes the case for first writing specs before beginning to vibe code.

Bertha.ai was one of the first WordPress AI assistants that was at one point very popular. Now it has exited from the WordPress plugin directory.

Do you want to make your content easier for AI to consume? Joost de Valk created a Markdown plugin that provides a markdown link in the post header. If I recall correctly, something similar may be under consideration for core.

Jamie Marsland contemplates the world his children are inheriting.

WordPress 7.0 will include the Abilities API, MCP Adapter, and the WP AI Client interface which can be used together for plugin, theme, and content creation.

Over on the Make blog the first AI guidelines for WordPress have been published. The idea is to set expectations on the use of AI in contributing.

Here is an interesting article from Dries, leader of the Drupal project, about the challenges or AI for project maintainers and the approach that Drupal is taking. It was interesting to note that in the case of finding security issues, that when used by experienced developers AI increased productivity, but when used by inexperienced devs it put a large burden on maintainers to investigate phantom security issues.

The AI team has introduced a tool to evaluate how well an AI understands WordPress. It is in its early stages, so it is not super complete, but can be useful in the future for gauging AI models for use.

There are some good insights in this thought piece by Chris Lema. Code abstraction is nothing new. Do you want to be in the front driving, or in the back complaining?