This post is part of the 🏔 Our Tech Journey track of 🔮 Crafting Tech Teams where we cover podcast episodes hosted by Denis on engineering culture topics covering extreme programming, technical coaching and team collaboration.
We got to sit down with Ferry de Boer to discuss the state of static analysis tools such as nDepend and Codescene.
Static analysis tools are often employed by architects and technical leaders who require a zoomed out perspective over a complicated system. Legacy codebases can grow into a tangled ball very quickly.
Maintenance costs can soar due to neglect or simply not knowing how to address shortcomings in a legacy system with a vast history of different software practices and evolving constraints.
In this episode we went over the common scenarios on
What tools fit which problem
What information and metrics are useful for insights
Next steps and trade offs for architects and tech leads alike
Timestamps
00:16 Diving Into Software Engineering: Coupling and Cohesion
03:53 The Journey from Freelancing to Consulting in Software Engineering
05:21 Interactive Discussion on Coupling, Cohesion, and Software Tools
31:49 Exploring the Impact of Cohesion and Coupling on Software Maintainability
33:12 Technical Demonstration: Analyzing Code for Cohesion and Coupling
36:35 Exploring Code Cohesion and Refactoring Strategies
38:02 Understanding Lack of Cohesion Metrics
39:49 Visualizing Code Metrics with Tools
44:26 Deep Dive into CodeScene Analysis
55:24 Comparing CodeScene and NDepend
01:08:38 Strategies for Implementing and Understanding Code Analysis
01:16:13 Decoding Dependency Structures in Code
01:17:31 Triangulation and Code Cohesion Insights
01:25:16 Layering and Dependency Management in Architecture
01:40:22 Technical Debt, Dependency Injection, and Pipeline Trust
01:53:44 Concluding Thoughts on Code, Culture, and Consulting
Share this post