Recommendations to others considering NDepend:
Prior to last year's updates, I would recommend you give NDepend to your team leads. Now, I would keep that recommendation and also add any up-and-coming power-users to the set who would benefit from the visualizations that NDepend offers for your code. It's also worth it to consider a build server integration license.
NDepend serves a lot of different scenarios, but it's going to amplify the best people on your teams. Review collected by and hosted on G2.com.
What problems is NDepend solving and how is that benefiting you?
NDepend serves a number of key scenarios:
- It helps me track technical debt trends over time
- It helps me identify the weaker areas of my own code
- It helps me visualize my code by diagramming the larger context
- It highlights issues I might not have seen
- Some editions can be integrated into my build pipeline to conduct automated analysis of all code and potentially reject code with insufficient quality or testing
Probably the biggest benefit I've seen in a workplace is the usage of NDepend visualizations to help explain technical debt to management and justify projects to remedy key issues in code. It gave me the tools I needed to pick the right battles and win those battles. Review collected by and hosted on G2.com.