Code reviews are integral to the software development lifecycle, crucial in maintaining code quality and promoting team collaboration. In this blog, I want to explore the importance of code reviews, tools, and practices to enhance the code review process and emphasize best practices specific to Dart and Flutter development. We will also discuss advanced concepts like "Shifting Left" to integrate reviews earlier in the development cycle, minimizing issues before they propagate.

There's a prevailing myth in software development that less code is always better. While concise code can benefit specific contexts, it doesn't necessarily equate to better code. Code quality, maintainability, and readability are often far more important than simply being less.

This article will explore why writing more code can often lead to better software, especially in Dart and Flutter applications. We'll focus on clarity, modularity, flexibility, robustness, and error handling. We'll also discuss the drawbacks of "magic" code and the importance of linting and rules in maintaining code quality.

Today we’re excited to announce the release of DCM 1.19.0!

This release includes 9 new rules (4 for Riverpod), proper support for codegen packages by the check-dependencies command, new summary output to sdterr for various reporters, new visualization of the statically resolved widget trees for analyze-widgets, new fix type for removing unused files (moved from check-unused-files), documentation updates and other DX improvements! 🚀

Let's go through the highlights of this release! (And you can find the full list of changes in our changelog)

Maintaining consistent and high-quality code is necessary in the fast-paced software development world, especially in Flutter and Dart projects, as they are known for being speedy tools. Continuous Integration (CI) has emerged as a crucial practice that helps development teams achieve this goal. CI provides rapid feedback by integrating code frequently and automating various aspects of the development process, allowing teams to identify and rectify issues early.

This article explores the significance of CI in enforcing code quality and consistency, the role of lint tools, especially DCM, and practical examples of integrating these tools with CI pipelines.

Today we’re excited to announce the release of DCM 1.18.0!

This release includes 8 new rules, improved "New Version" notifications, new grouping option for IntelliJ plugin, automatic DCM version detection by the "setup-dcm" action and general UX improvements 🚀.

Let's go through the highlights of this release! (And you can find the full list of changes in our changelog)

On any real-world Flutter project (but any project, really...), you want to run an analyzer and a linter at some point to ensure your quality matches the baseline your team agreed on. If you've been following me for some time, you might know that I love a promising CI/CD pipeline (heck, I even wrote a series on the topic 🙃). I always recommend running these checks in your CI pipeline.

Today we’re excited to announce the release of DCM 1.17.0!

This release includes 9 new rules (3 for Riverpod 🔥), early access to the DCM Teams license management portal, per-package monorepo mode, global configuration with DCM version constrains and more 🚀.

Let's go through the highlights of this release! (And you can find the full list of changes in our changelog)

Today we’re excited to announce the release of DCM 1.16.0!

This release includes 2 new commands (one for the advanced analysis of parameters and another one for the project structure analysis), 5 new rules, UX improvements and more. 🚀

Let's go through the highlights of this release! (And you can find the full list of changes in our changelog)

Today we’re excited to announce the release of DCM 1.15.0!

This release includes extension types support for all existing rules and features, 13 new rules (4 for extension types), 30 new quick fixes (some of them are available via dcm fix), Checkstyle format for all available commands, UX improvements and more. 🚀

Let's go through the highlights of this release!

Today we’re excited to announce the release of DCM 1.14.0!

This release includes a new command to find duplicate functions, methods and constructors, new built-in preset to avoid installing an additional package, 4 new rules, and more 🚀.

Now let's go through the highlights of this release 🚀.

Today we’re excited to announce the release of DCM 1.13.0!

This release includes similar widgets report, improved unused code IDE integration and a new mode, 8 new rules, unused files in IDE, performance improvements, and more 🚀.

Now let's go through the highlights of this release 🚀.

Today we’re excited to announce the release of DCM 1.12.0!

New command to run multiple DCM checks at once, 7 new rules (3 for FlutterHooks), custom analysis_options files support, performance improvements (with ~58 fully rewritten rules and fixed freezes of the IntelliJ plugin) and more 🚀.

Now, let’s go on a quick journey together to explore all updates!

Today we’re excited to announce the release of DCM 1.11.0!

New command to analyze the quality and usage of your widgets, 20 new rules (with 6 of them to help enforce the Flutter style guide 🔥), ~30 rules updated, redesigned HTML reports with, of course, dark mode support 🚀!

Now, let’s go on a quick journey together to explore all updates!

Today we're excited to announce a new license type: open source project licenses!

Working on open source is difficult because you usually have to work late at night or on weekends, which makes every minute count but also increases the chance of error. This is where DCM can help. Enabling DCM rules helps reduce the time spent fixing tricky bugs and reviewing code. It can also help you align the coding style between your regulars and new contributors.

Today we’re excited to announce the release of DCM 1.10.0!

New command to deactivate the current device to help you manage your license activations, 14 new rules, general UX improvements and displaying the recommended rules for the Trail licenses by default 🚀.

Let’s go on a quick journey together to explore all updates!