While the benefits of using static analysis tools such as DCM are quite obvious, integrating them into an existing project can be challenging due to the many possible warnings that need attention. That's why developers prefer to add such tools in the early stages of a project and quickly give up when it comes to old existing codebases.

But when it comes to DCM there are several tricks you can use to significantly reduce the time spend on its integration.

Considering that DCM is a paid product, it's reasonable to raise the question of what value a company will receive from using it.

Let's calculate the return on investment (the ratio between income and costs) from using DCM in the development process. Hopefully it will help you fully realize the rationality behind it.

We all make mistakes, it's a part of our developer journey. But there are different tools that can help us in our way of creating great software that helps other people. DCM (formerly Dart Code Metrics) is a great example of such a tool. It is a static analysis tool that detects the quality and consistency issues helping you reduce the number of bugs and deliver results faster to your users.

But before we begin, what does static analysis actually mean? Well, static analysis is the automated analysis of source code without executing the application. It does not know anything about how the code will be run, what actual data it will work with, etc. A good example of such tools is the Dart analyzer (you probably have it running right now, even if you are no aware of it) and any tool that is a linter.

How does it work? It would take a book (or maybe even two) to describe it in details, but in short, it runs a separate process that is able to parse your code into set of tokens, build AST and validate it based on some rules.

And yes, dynamic analysis also exists 🙂.

Let's take a look at the various problems that you might encounter in your code and how DCM can help you find them together.

New month, new DCM release! Today we’re excited to announce the release of DCM for Teams 1.3.0! In this version we completely reworked metrics (plus added new ones), added long promised baseline support, added support for applying dcm fix on save, new rules and more!

Let’s go on a quick journey together to explore all the new features!

Today we’re excited to announce the release of DCM for Teams 1.2.0! In this version we focused on improving dcm fix, cleaned up false-positives in the unused code check, added 22 new rules, fixed false-positives in existing rules and more!

Let’s go on a quick journey together to explore all the new features!

Today we’re excited to announce the release of DCM for Teams 1.1.0! In this version we improved the unused code check (now it can check for separate fields and methods), added two new commands: dcm check-exports-completeness and dcm fix, ten new rules and small improvements like highlighting the unused // ignore comments and reanalysing all the files after the config is changed.

Let’s go on a quick journey together to explore all the new features!

2022 was a huge year for DCM - 26 releases, 32 new rules added, a lot of existing rules improved, several new commands (like check-unused-code and check-unnecessary-nullable-parameters) added, but we received a lot of feedback that the current IDE integration scales poorly and it's a real pain to use DCM on large projects.

So that's why today we're excited to present you a version that still focuses on helping you build better software, but also aims to scale with your codebase - DCM for Teams!