I used to enforce heavy pre-commit hooks to optimise for fast feedback. These days, I push most of those checks to CI.
This post isn’t about tooling so much as it is about flow state, cognitive load, and learning the cost of enforcing the right checks at the wrong time.
There’s a point in a long, complex project where you stop noticing the shift happening. You’re answering a few more questions, stepping into a few more decisions, translating a few more ambiguities.
And then one day you realise the project isn’t just something you work on anymore. It’s something you carry.
Coding agents don’t fail because the model is weak. They fail because the environment they land in is noisy, inconsistent or ambiguous. This post shows senior engineers and tech leads how to reshape one slice of a real-world repo so agents behave predictably instead of drifting.
AI writes TypeScript with calm confidence but feels far less predictable in PHP. After digging into why, I realised the difference had nothing to do with the model and everything to do with structure. TypeScript gives AI clear signals. PHP often gives it none. In this post, I break down why that matters and how you can bring that same clarity into PHP and WordPress today.
When I stopped treating AI like a magic code machine and started treating it like a product manager and a junior engineer, everything got easier. Clearer requirements. Faster delivery. Much calmer engineering.
On a long-running headless multisite project, our code review process slowly spiralled out of control, with 100+ open PRs, slow turnarounds, constant context-switching, and frustrated engineers. We fixed it by reframing how we think about reviews, creating a clear hierarchy, and making readability the foundation. This is the story of how we made code reviews calmer, faster, and far more...
In my last post, I discussed the general tech stack that I’ve been using lately for Headless WordPress builds. One of the main components of this stack is Repress. Repress is a small library written by Ryan McCue from Human Made that works with Redux and allows you to access your WordPress REST API data easily and with minimum fuss. It contains a number of higher-order components (HOC) that...
Recently I’ve spent a fair amount of time building up React websites using WordPress as the data source. This has been a very interesting period of learning for me, coming from a PHP background and as such, I’m going to write down my thoughts on the process in the hope that it can help others approaching this task! Why go headless? In my case, the reason for going headless was...
I was working on a project this week that required me to zoom in to a marker on a Google map. That’s easy, I thought, there must be a method for doing that within the V3 API. I was wrong. Apparently Google are fine with adding a panTo() method for smoothly panning to a marker, but the setZoom() method re-draws the map canvas and jumps straight to the zoom level you set.“ There are a...
A bit of a background, I’ve recently been working on a reasonably large, headless, multilingual WordPress build. The frontend and the backend needed to be hosted on separate domains, so we decided to build this site using the following technologies: Backend: WordPress via the REST API JWT Authentication for the API WPML for i18n ACF Pro for custom fields. Frontend: React Redux i18next All...