Positions we hold, and the reasoning behind them.
Writing on the decisions that determine whether software is worth what it cost: build versus buy, integration reliability, modernisation, and designing systems that outlast their authors.
Technology strategy
·6 min read
Build or buy: the question underneath the question
Build-versus-buy is rarely a technology decision. It is a decision about which parts of your business you are willing to let someone else define.
Engineering
·7 min read
Why integrations fail, and what reliable ones do differently
Most integration failures are not caused by the API. They are caused by assumptions about delivery, ordering and duplication that were never true.
Engineering
·6 min read
Writing software that outlives the people who wrote it
The real test of a system is not whether it works on launch day. It is whether a developer who has never seen it can change it safely two years later.
Modernisation
·5 min read
Before you rebuild it, find out what it actually does
Rewrites fail for a consistent reason: the replacement handles the documented behaviour and not the accumulated exceptions the business quietly depends on.
Disagree with any of this?
These are positions, not neutral summaries. If your situation contradicts one of them we would genuinely like to hear why. That conversation is usually more useful than the article.