We write when we learn something worth passing on — usually after an engagement surfaces a problem we had not seen framed properly anywhere else. No posting schedule, no SEO filler.
Showing 4 posts.
Applied AI7 min
Everyone tests retrieval systems for made-up answers. Almost nobody tests them for correctly-sourced answers shown to the wrong person — which is the failure that ends up in a breach notification.
Cloud6 min
Two weeks of discovery feels like two weeks of nothing happening. It is the cheapest insurance available on a migration, and the reason most overruns are decided before any workload moves.
Security6 min
A list sorted by CVSS score is not a priority order, because severity is a property of a vulnerability and risk is a property of your network. Here is what to ask for instead.
Software7 min
You do not need to know why a behaviour exists to protect it while you work around it. This is the technique that makes legacy modernization survivable — and the one most teams skip.
Most of what we write about started as a client engagement. If a post describes your situation more accurately than you'd like, that's usually a good reason to talk.
