$ cat author.md
Author
I'm Chris, a software engineer who ended up caring most about software architecture: how systems are shaped, where their boundaries sit, and why some codebases stay pleasant to change for years while others calcify by the second sprint.
I've been writing PHP since PHP 3, back when "architecture" meant deciding which include file held the
database connection and objects were something that happened to other languages. I've followed it through
every major version since, and I'm still happily writing it, which says as much about PHP as it does about me.
How I think about architecture
- Architecture is about change. A good structure makes the likely changes cheap, and is honest about which ones will be expensive. Everything else is decoration.
- Decisions over diagrams. Every boundary and abstraction should have a reason you can write down, along with the trade-off it accepts. If nobody can explain why a layer exists, it probably shouldn't.
- Start simple, keep seams. A modular monolith with clear boundaries beats premature microservices. Extract a service when the boundary has proven itself, not when the conference talk was convincing.
- Let constraints shape the design. Platform limits, team size and budget are architectural inputs, not afterthoughts. A read-only filesystem on Lambda is a design requirement, not an inconvenience.
What I write about
- PHP and Laravel: the language and framework I know best. Modern PHP, clean domain code, sensible use of the framework, and knowing when to step outside it.
- Data: years with relational databases (schema design, indexing, query tuning, migrations that don't take the site down) and non-relational ones (key-value and document stores, caches, queues). Picking the right store for the job, rather than the one that was already running.
- Cloud and Lambda: serverless and managed services, mostly on AWS, with a soft spot for AWS Lambda in general, not just for PHP. I liked it enough to write my own Python framework built specifically for Lambda: cold starts, event sources and the "every invocation is a fresh start" mindset as first-class concerns, rather than a web framework squeezed into a function. Plus infrastructure as code, and a healthy interest in what the monthly bill says about the architecture.
- Security: treating it as part of the design, not a checklist at the end. Patching early, reducing attack surface, and reading advisories before they become incidents.
- A bit of AI: using it where it genuinely helps build and run software, and staying sceptical where it doesn't. Fewer predictions, more experiments.
On GitHub
Currently working with
- PHP 8.5, Laravel, Livewire and Tailwind CSS
- AWS Lambda: PHP via Bref, Python via my own framework
- Aurora PostgreSQL, DynamoDB
- Domain-driven design, modular monoliths and event-driven architecture