The latest articles on DEV Community by leonids2005 (@leonids2005). https://dev.to/leonids2005 https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F664457%2Fd6e5bf52-c351-4bb2-8a37-2f1cf9af2244.jpeg https://dev.to/leonids2005 en leonids2005 Thu, 26 Feb 2026 11:27:27 +0000 https://dev.to/leonids2005/we-can-measure-how-fast-we-ship-can-we-measure-how-well-we-understand-what-we-built-5amm https://dev.to/leonids2005/we-can-measure-how-fast-we-ship-can-we-measure-how-well-we-understand-what-we-built-5amm <p>Margaret-Anne Storey recently flagged measurement of cognitive debt as an open research question. We have plenty of metrics for delivery speed — DORA, cycle time, merge frequency — but nothing that tells us whether the team that shipped a feature actually understands it.</p> <p>This article proposes a concrete starting point: the Feature Comprehension Score. At the close of each feature, an AI generates a short assessment from the development artefacts, and team members answer independently. The score maps to Naur's three layers of program understanding — domain intent, design justification, and modification capacity.</p> <p>I'd love to hear from anyone who has tried measuring comprehension in their teams, formally or informally.</p> <p><a href="https://medium.com/gitconnected/we-can-measure-how-fast-we-ship-can-we-measure-how-well-we-understand-what-we-built-a5ad2749c8fa" rel="noopener noreferrer">https://medium.com/gitconnected/we-can-measure-how-fast-we-ship-can-we-measure-how-well-we-understand-what-we-built-a5ad2749c8fa</a></p> ai productivity software softwareengineering