I went to DrupalCon Rotterdam 2026. This is what I learned #4: Stop letting AI blindly guess your bugs! ๐ค๐
I attended "Agentic Debugging: Teaching AI to Step Through Your Code" by Kyrylo Popov. AI assistants are great at reading code, but when a bug hides in runtime state, they are completely blind. They usually just guess the fix or tell you to add random var_dump statements.
The missing link? Connecting AI directly to Xdebug via MCP. Instead of guessing, the AI actually steps through your running code to prove the bug!
Why you should start using it:
- Force your AI to gather real runtime facts instead of hallucinating fixes.
- Visual UI Mode lets you sit back and watch Copilot click "step in/out" right inside your VS Code debugger.
- Lightning fast "Plan Mode" makes the AI write a debug_plan.json hypothesis and execute it headlessly in ~4 seconds.
- No "AI Magic" - the agent does the tedious investigation, leaving the final code review and fix to you.
Want to see it in action? The project is at GitHub! Check out the MCP server for PHP/Xdebug here: https://t.co/DlmPbjY9yQ
Time to give your AI some eyes! ๐ #Drupal #DrupalCon #AI #PHP #Debugging #VSCode
I went to DrupalCon Rotterdam 2026. This is what I learned #3: Stop the "boiling frog" performance regressions! ๐ธ๐ฅ
I attended "Performance Testing in the Wild" by Julien Joye. Performance debt usually sneaks in silently - one extra SQL query or cache miss per commit - until your site is boiling hot and incredibly slow.
The hidden gem to fix this? Drupal Core's PerformanceTestBase class. You state in test different db query and cache counts for page - if they change, tests will fail.
Why you should start using it:
- Catch performance regressions in CI, not in production.
- Tests deterministic metrics (exact query counts, cache ops) so CI isn't flaky.
- Pair it with Gander & Grafana to visually trace why a test failed.
- Coming in D11.5: Auto-generated baseline budgets via YAML files!
Want to see it in action? Check out how the Umami profile uses it in core:
https://t.co/GLZrCY34rj
Time to build that safety net! #Drupal #DrupalCon #WebPerf #PHP #CI
I went to DrupalCon Rotterdam 2026. This is what I learned #2: Drupal 11 finally has a built-in CLI!
I attended "A joyful tour through the CLI" by Drush maintainer Moshe Weitzman (Drupal uid 23!). The new CLI is invoked with dr (vendor/bin/dr; ddev dr), which Moshe affectionately calls "Doctor". ๐ฉบ
Why switch to dr?
- It's faster than Drush (skips the heavy bootstrap/pre-flight)
- Built on clean Symfony console code & PHP attributes
- Piggybacks on Core's localization for translated commands
Drush will still be around for D12, but dr is the future out-of-the-box experience. Time to start playing with it! ๐ #DrupalCMS #Drupal11 #PHP @weitzman
I went to DrupalCon Rotterdam 2026. This is what I learned #1: Drupal is light-years ahead of its reputation.
As @Dries noted, it's embracing the future. Between Canvas, MCP servers, and D11 speed, it feels like a brand-new toy.
Read my full recap: https://t.co/PvqvPpiWsr
#DrupalCMS
@elonmusk Create Tesla +1, create SpaceX +1, buy Twitter -1, want a cage match with Zuckerberg -1, ridicule a man whose country is being invaded -1. I feel like we're heading for Idiocracy.
@stevenic@johnrush I made a small benchmark script with Claude month ago, this week I needed some adjustment, but instead before I could request my wishes, it added it's own upgrades already and these were good! Eg instead of listing each Url, it added progressbar and how long it'll take to finish