May 2 · 4 min read · Why Severity Is Broken at Most Companies Everyone has severity levels. Almost nobody agrees on what they mean. Ask ten engineers what SEV-2 means and you'll get eight different answers. This causes: Under-paged incidents (people thought SEV-3 meant ...
Join discussion
Apr 19 · 3 min read · The Monday Morning Disaster Every Monday, the same story: the incoming on-call engineer has no idea what happened over the weekend. The outgoing engineer left a cryptic Slack message at 11pm and went to bed. We lost 2 hours every Monday rebuilding co...
Join discussionMar 25 · 5 min read · Last year I started working on a large, unfamiliar codebase. Go, new CI/CD pipelines, new deployment patterns. My job was integration work, not security. I was using AI to accelerate my understanding of the system, reading through services, tracing d...
Join discussionMar 25 · 7 min read · I recently published a four-part series on AI code review, correlated errors, and specification-driven verification. The research behind it took longer than the writing. This post is about that research process, not the conclusions it produced. The a...
Join discussionMar 10 · 6 min read · The biggest obstacle to AI in software engineering isn't the technology. It's trust. Teams don't trust AI-generated code. And they shouldn't, not blindly. But the conversation in most engineering organisations has stalled at that point. The distrust ...
Join discussion
