# Daryll Doyle: Calm WordPress architecture \& DevEx Generated by Yoast SEO v28.6, this is an llms.txt file, meant for consumption by LLMs. ## Pages - [Controlled Acceleration](https://enshrined.co.uk/controlled-acceleration/) - [Home](https://enshrined.co.uk/) - [Hi, I’m Daryll\.](https://enshrined.co.uk/about/) - [Blog](https://enshrined.co.uk/blog/) - [Parallelize WordPress Downloads](https://enshrined.co.uk/parallelize-downloads/) ## Posts - [What is code review for, when agents write the code?](https://enshrined.co.uk/2026/09/30/what-is-code-review-for-when-agents-write-the-code/): In 2024 I wrote about fixing code review after it became our team's bottleneck\. Everything in that post assumed a person had written the code\. Most of my code is now written by an agent, and those PRs can wait a week for review\. This post goes back through my old review hierarchy and asks who checks each layer now\. It also covers what I check instead, and where that approach breaks\. - [The Model in Practice](https://enshrined.co.uk/2026/03/01/the-model-in-practice/): Six issues describing five phases, and I don't use them that way any more\. Plan, specify and constrain have collapsed into a single conversation\. The collapse is the success condition rather than a failure\. The five phases remain the fastest way to diagnose work that has gone sideways, even when they're no longer sequential steps\. - [Skills as a Type System for AI](https://enshrined.co.uk/2026/02/15/skills-as-a-type-system/): Ad\-hoc prompts produce inconsistent documentation because the AI doesn't know your standards\. You can hand a junior engineer a style guide; with prompts there is no equivalent\. So I built one\. Encoding standards as reusable skills works like a type signature — constrain the input and the output, and the shape of the work stops drifting\. - [Tests as Verification, Not Ceremony](https://enshrined.co.uk/2026/02/08/tests-as-verification-not-ceremony/): When AI writes code at volume you can't read every line, and you shouldn't have to\. Tests become how you verify output without parsing the implementation\. This is about why most coverage targets are theatre, and the question worth asking instead: if I read only the tests, would I know whether this code is correct? - [Planning Is the Highest\-Leverage Work](https://enshrined.co.uk/2026/02/01/planning-is-the-highest-leverage-work/): If you skip planning and go straight to "build this", the AI will invent a plan for you\. It won't reflect your domain, your constraints, or what you actually need\. This covers which planning artefacts earn their keep — PRDs, mapping docs, statements of intent — and a short readiness checklist for deciding whether work is ready to hand over\. ## Categories - [WordPress](https://enshrined.co.uk/category/wordpress/) - [PHP](https://enshrined.co.uk/category/php/) - [AI](https://enshrined.co.uk/category/ai/) - [Controlled Acceleration](https://enshrined.co.uk/category/controlled-acceleration/) - [Plugins](https://enshrined.co.uk/category/plugins/) ## Tags - [process](https://enshrined.co.uk/tag/process/) - [Code Reviews](https://enshrined.co.uk/tag/code-reviews/) - [Tooling](https://enshrined.co.uk/tag/tooling/) ## Optional - [Sitemap index](http://enshrined.co.uk/sitemap_index.xml)