Notes on data, AI, IT
and security
No marketing fog. The way I think about real problems with founders and managers.
API-first or integration spaghetti: the choice your architecture makes
Why the way your company's systems talk to each other determines growth speed and the cost of change.
Why cloud migrations run long: three systemic reasons
Cloud migrations almost always take longer than planned. Three causes I see consistently, and how to work with them.
API as a product: why internal integrations fall apart
How the approach to internal APIs affects the reliability of the whole architecture, and why an internal client deserves no less respect than an external one.
Feature flags in production: the promise and the maintenance debt
Feature flags let you ship safely and experiment cheaply - but every flag you add is a piece of logic you have to eventually remove.
Kubernetes for small business: when orchestration is overkill
Why complex infrastructure often slows small teams down, and how to match the level of complexity to the actual task.
COVID, remote work, and the sudden maturity of the digital workplace
The pandemic accomplished in a few months what corporate IT strategies had failed to do in years. What changed in the digital infrastructure of companies - and what will stick.
The cloud bill that arrived after the fast migration
Companies that rushed to the cloud under pandemic pressure are now receiving bills nobody planned for. Why this happens and what to do about it.
Business continuity after the pandemic: what to revisit in the architecture
What conclusions about IT architecture and operational resilience are worth drawing from the first wave - before normal routine returns.
Digital workplace: from emergency fix to something sustainable
How to move from 'just make it work' to a proper infrastructure for a distributed team - observations from April 2020.
Event-driven architecture: a plain explanation for non-engineers
What event-driven architecture is, why engineering teams want it, and how to evaluate whether it makes sense for your product - without needing to understand the code.
API-first design when the team works remotely
Why distributed teams make sloppy API contracts visible faster - and how to use that pressure to establish a more disciplined design process.
Remote work in a weekend: what broke and what held
First observations on how companies are handling the emergency shift to remote in March 2020.