Writing
Practical writing on platform migrations, technical leadership, and the software problems that actually matter to growing businesses.
Platform migrations fail not because of bad technology, but because of underestimated scope, ignored data debt, and the fallacy that switching platforms solves business problems.
Technical debt isn't just slow feature development. It's compounding interest that erodes team morale, drives away senior engineers, and eventually makes your codebase unmaintainable. Here's how to quantify it.
RSC is not a drop-in replacement for client-side React. It's a different mental model that rewards careful boundary design and punishes component architectures that weren't built with the server in mind.
After a decade of failed generic software deployments, law firms are discovering that their workflows are too specialised for off-the-shelf solutions—and that custom software, done right, pays for itself in 18 months.
PrestaShop to Shopify migrations are among the most technically complex in e-commerce. Here's the step-by-step process we use—from catalog audit through DNS cutover—with the gotchas that catch most teams off guard.
On Black Friday, our payment platform processed 847 transactions per second at peak. Zero downtime. Zero data loss. Here's the architecture—idempotency keys, event-driven processing, circuit breakers, and the reconciliation nobody writes about.
The senior engineers who pitched your project are not building it. Here's the agency business model nobody explains to clients—and the questions you need to ask before signing anything.
Every mobile project starts with 'we want iOS and Android and shared code.' Fine. But let's talk about what you're actually signing up for—the performance ceiling, the architecture choices, and when native wins.
Somewhere between 5,000 and 15,000 active users, most SaaS architectures start grinding. The failure modes are predictable: database bottlenecks, synchronous processing under load, missing connection pooling. Here's the fix sequence.
The CTO called on a Thursday. Fourteen months, £200K, and a product that didn't work. Here's what I found in the first 48 hours—and how I turned it around before the board meeting.
Three years after Consumer Duty came into force, firms are still signing off 'compliant' while their architecture tells a different story. Here's what the regulation actually requires from your tech stack.
I spent three years getting good at Kubernetes. Then I started a consultancy and stopped using it for 80% of projects. This is not a clickbait story about Kubernetes being bad. It's a story about matching tools to problems.