Skip to content
← All posts

Engineering

PHP, Laravel, queues and schemas: the unglamorous decisions that settle whether an app is still pleasant to work on in year three.

6 posts

Engineering6 min read

I would not start a new app in PHP

The strongest argument for PHP was never technical. It was that you could hire for it cheaply and host it anywhere. One of those two reasons has quietly stopped being true.

Engineering6 min read

How to patch PHP in a hurry without breaking production

PHP ships an out-of-band fix for two critical flaws at 14:00 UTC today. Here is the hour of preparation that turns the patch into a non-event, and the runbook for when it lands.

Engineering3 min read

The N+1 you cannot see

Everyone knows to eager load. The queries that actually take sites down are the ones hiding in an accessor, a Blade partial, or a policy. There is a one-line switch that finds all of them.

Engineering3 min read

Queues are not optional

If your request handler calls somebody else’s API, you have already built a distributed system. The queue is how you stop their bad day from becoming your bad day.

Engineering4 min read

Database indexes, explained with a phone book

Most slow queries are one index away from being fast. The reason people do not add it is that nobody ever explained what the index is actually doing.

Engineering3 min read

PHP got good and nobody told you

If your mental image of PHP is from 2014, it is wrong in ways that would change your architecture. Here is what actually landed, and which parts change how you write code.