Notes on data, AI, IT
and security
No marketing fog. The way I think about real problems with founders and managers.
An API is a contract, not a piece of code
Why the interface between systems matters more than the implementation behind it, and what that means for how you manage integrations.
Microservices: what the term means for business
A breakdown of what actually sits behind the word 'microservices' and how a manager should think about this architectural choice.
Docker 1.0 and the new discipline of release
The Docker 1.0 release is not about containers. It is about the runtime environment becoming as manageable and reproducible as the code itself.
Microservices: architectural choice or management decision
Why moving to microservices is not purely a technical decision, and what a founder needs to understand before such a project starts.
Technical debt: what it means for non-technical founders
An explanation of technical debt through a management lens - where it comes from, how to measure its business impact, and when to pay it down.
What to read and watch in 2014 if you are building a system, not a career in hype
A closing post for the year that gives the reader a map of directions, not just a list of fashionable words.
Postdiction 2014-2016: containers, semantics and cloud will grow together, not separately
The winner will not be a single technology stack, but companies that can combine several waves into one platform.
The year in one frame: cloud trust, semantics, containers and a new maturity of the agenda
2013 is changing not the tools, but the direction of architecture and trust in IT.
The platform team as the next step after strong operations
Why a centralised platform is becoming a separate function, and what that means for an IT leader.
Cloud exit plan: contract, migration, and the exit test
While everything is working, nobody calculates the cost of leaving. That is exactly why it needs to be calculated before it becomes urgent.
What 2014 will demand from architecture: fewer monoliths, more discipline
The preparation is not about buzzwords - it is about faster release cycles and service connectivity. That requires specific architectural decisions made now.
Team contracts: APIs and data cannot run on trust alone
Why internal interfaces require explicit expectations - around structure, quality, and how changes are handled.