{"content":"Quoting Ally Piechowski\n\n> Questions for developers:\n> \n>  * “What’s the one area you’re afraid to touch?”\n>  * “When’s the last time you deployed on a Friday?”\n>  * “What broke in production in the last 90 days that wasn’t caught by tests?”\n> \n> Questions for the CTO/EM:\n> \n>  * “What feature has been blocked for over a year?”\n>  * “Do you have real-time error visibility right now?”\n>  * “What was the last feature that took significantly longer than estimated?”\n> \n> Questions for business stakeholders:\n> \n>  * “Are there features that got quietly turned off and never came back?”\n>  * “Are there things you’ve stopped promising customers?”\n\n— Ally Piechowski, How to Audit a Rails Codebase\n\nTags: technical-debt, software-engineering, rails","contentType":"text/plain;utf-8","attachments":[],"quotePin":""}