Original: Simon Willison · 06/03/2026
Summary
Ally Piechowski shares insightful questions for developers, CTOs, and business stakeholders to audit a Rails codebase effectively.Key Insights
“What’s the one area you’re afraid to touch?” — Question for developers
“What feature has been blocked for over a year?” — Question for the CTO/EM
“Are there features that got quietly turned off and never came back?” — Question for business stakeholders
Topics
Full Article
6th March 2026 Questions for developers: “What’s the one area you’re afraid to touch?” “When’s the last time you deployed on a Friday?” “What broke in production in the last 90 days that wasn’t caught by tests?” Questions for the CTO/EM: “What feature has been blocked for over a year?” “Do you have real-time error visibility right now?” “What was the last feature that took significantly longer than estimated?” Questions for business stakeholders: “Are there features that got quietly turned off and never came back?” “Are there things you’ve stopped promising customers?” — Ally Piechowski, How to Audit a Rails CodebaseRelated Articles
I'm Boris and I created Claude Code. I wanted to quickly share a few tips for using…
Boris Cherny · how-to · 53% similar
My fireside chat about agentic engineering at the Pragmatic Summit
Simon Willison · explanation · 52% similar
A couple of days ago, I sat down with Vivek Bharathi and dumped my brains. Here's the interview...
Geoffrey Huntley · explanation · 52% similar
Originally published at https://simonwillison.net/2026/Mar/6/ally-piechowski/#atom-everything.