……每当我加入新的开发团队时，这类工具都能帮我摸清团队协作和交付的动态。这个工具尤其棒，让我想起了前阵子读过的一本书——Adam Tornhill 写的《Your Code as a Crime Scene》[1]。Adam 试图阐述的思路和这类似，但他把整个理念提升到了一个新境界，讲解了如何利用 git 历史来挖掘技术债和隐藏的耦合……
…tools like these have been helping me to understand the team's and delivery dynamics when I'm joining new dev-teams. This particular is great, as it reminds me of a book that I had read a while back; Your Code as a Crime Scene [1] by Adam Tornhill. Adam is trying to explain something similar, but takes the whole concept onto the next level by explaining how tech debt and hidden coupling can be discovered using the git history…
想要对代码复杂度进行这种经验性度量，最好的参考资料就是 Adam Tornhill 的《Your Code as a Crime Scene》。另请参阅 http://www.adamtornhill.com/code/codemaat.htm
The best source for this kind of emprical measurement of code complexity is Your Code as a Crime Scene by Adam Tornhill. See also http://www.adamtornhill.com/code/codemaat.htm
我很喜欢这种思维方式，它让我想起了 Adam Tornhill 的《Your Code as a Crime Scene》：https://www.adamtornhill.com/articles/crimescene/codeascrime... 另外，还有一个稍有牵连的概念是“开发者遗留指数”（Developer's Legacy Index）：https://www.javaadvent.com/2021/12/using-jgit-to-analyse-the...
I like the mindset, it reminds me of "Your code as a crime scene" by Adam Tornhill: https://www.adamtornhill.com/articles/crimescene/codeascrime... Also, very tangentially, to the notion of the Developer's Legacy Index: https://www.javaadvent.com/2021/12/using-jgit-to-analyse-the...
……而且像传递过多参数、或者对某些代码变更评估“爆炸半径”这类“代码异味（code smells）”，不过是在捕捉缺乏“代码理论（code theory）”所带来的副作用罢了。关于这个话题有一本很有意思的书叫《Your Code as a Crime Scene》。核心问题在于，我们在没有真正搞懂根本问题是什么的情况下，一次又一次地试图去修修补补，这导致规则越来越多，而且极易被误读，除非……
…And "code smells" like passing too many parameters or doing "blast radius" for certain code changes are only watching for side-effects of a missing "code theory". An interesting book on the topic is "Your code as a crime scene". The bottom line is we're trying to fix these problems over and over again without having a good understanding of what the real problem is and this leads to too many rules too easy to misinterpret unless…
……《Algorithms to Live By》（算法是我们在写任何代码之前的基础思想）7. 《Pro Git》（软件离了版本控制系统（VCS）根本跑不起来。我们工作日的每分每秒都在用它）8. 《Your Code as a Crime Scene》（利用代码历史来排查代码中的问题）9. 《Designing Data-Intensive Applications》（数据库无处不在）10. 《Software Engineering at Google》（解决最大规模的扩展难题）特别提及：……
…Algorithms to Live By (Algorithms are fundamental ideas before we write any code) 7. Git Pro (Software cannot run without a Version Control System (VCS). We use it every minute of our working day) 8. Your Code as a Crime Scene (Finding problems in the code using code history) 9. Data-Intensive Applications (Databases are everywhere) 10. Software Engineering at Google (Addressing the biggest scaling problems) Honorable Mentions:…
看看 Adam Tornhill 的成果：https://github.com/adamtornhill/code-maat https://www.youtube.com/watch?v=hWhBmJJZoNM https://pragprog.com/book/atcrime/your-code-as-a-crime-scene https://pragprog.com/book/atevol/software-design-x-rays
See the work by Adam Tornhill https://github.com/adamtornhill/code-maat https://www.youtube.com/watch?v=hWhBmJJZoNM https://pragprog.com/book/atcrime/your-code-as-a-crime-scene https://pragprog.com/book/atevol/software-design-x-rays
……每当我加入新的开发团队时，这类工具都能帮我摸清团队协作和交付的动态。这个工具尤其棒，让我想起了前阵子读过的一本书——Adam Tornhill 写的《Your Code as a Crime Scene》[1]。Adam 试图阐述的思路和这类似，但他把整个理念提升到了一个新境界，讲解了如何利用 git 历史来挖掘技术债和隐藏的耦合……
…tools like these have been helping me to understand the team's and delivery dynamics when I'm joining new dev-teams. This particular is great, as it reminds me of a book that I had read a while back; Your Code as a Crime Scene [1] by Adam Tornhill. Adam is trying to explain something similar, but takes the whole concept onto the next level by explaining how tech debt and hidden coupling can be discovered using the git history…
想要对代码复杂度进行这种经验性度量，最好的参考资料就是 Adam Tornhill 的《Your Code as a Crime Scene》。另请参阅 http://www.adamtornhill.com/code/codemaat.htm
The best source for this kind of emprical measurement of code complexity is Your Code as a Crime Scene by Adam Tornhill. See also http://www.adamtornhill.com/code/codemaat.htm
我很喜欢这种思维方式，它让我想起了 Adam Tornhill 的《Your Code as a Crime Scene》：https://www.adamtornhill.com/articles/crimescene/codeascrime... 另外，还有一个稍有牵连的概念是“开发者遗留指数”（Developer's Legacy Index）：https://www.javaadvent.com/2021/12/using-jgit-to-analyse-the...
I like the mindset, it reminds me of "Your code as a crime scene" by Adam Tornhill: https://www.adamtornhill.com/articles/crimescene/codeascrime... Also, very tangentially, to the notion of the Developer's Legacy Index: https://www.javaadvent.com/2021/12/using-jgit-to-analyse-the...
……而且像传递过多参数、或者对某些代码变更评估“爆炸半径”这类“代码异味（code smells）”，不过是在捕捉缺乏“代码理论（code theory）”所带来的副作用罢了。关于这个话题有一本很有意思的书叫《Your Code as a Crime Scene》。核心问题在于，我们在没有真正搞懂根本问题是什么的情况下，一次又一次地试图去修修补补，这导致规则越来越多，而且极易被误读，除非……
…And "code smells" like passing too many parameters or doing "blast radius" for certain code changes are only watching for side-effects of a missing "code theory". An interesting book on the topic is "Your code as a crime scene". The bottom line is we're trying to fix these problems over and over again without having a good understanding of what the real problem is and this leads to too many rules too easy to misinterpret unless…
……《Algorithms to Live By》（算法是我们在写任何代码之前的基础思想）7. 《Pro Git》（软件离了版本控制系统（VCS）根本跑不起来。我们工作日的每分每秒都在用它）8. 《Your Code as a Crime Scene》（利用代码历史来排查代码中的问题）9. 《Designing Data-Intensive Applications》（数据库无处不在）10. 《Software Engineering at Google》（解决最大规模的扩展难题）特别提及：……
…Algorithms to Live By (Algorithms are fundamental ideas before we write any code) 7. Git Pro (Software cannot run without a Version Control System (VCS). We use it every minute of our working day) 8. Your Code as a Crime Scene (Finding problems in the code using code history) 9. Data-Intensive Applications (Databases are everywhere) 10. Software Engineering at Google (Addressing the biggest scaling problems) Honorable Mentions:…
看看 Adam Tornhill 的成果：https://github.com/adamtornhill/code-maat https://www.youtube.com/watch?v=hWhBmJJZoNM https://pragprog.com/book/atcrime/your-code-as-a-crime-scene https://pragprog.com/book/atevol/software-design-x-rays
See the work by Adam Tornhill https://github.com/adamtornhill/code-maat https://www.youtube.com/watch?v=hWhBmJJZoNM https://pragprog.com/book/atcrime/your-code-as-a-crime-scene https://pragprog.com/book/atevol/software-design-x-rays