What do you like best about the product?

I have used Codacy for various projects, both in closed and open source development. I found Codacy to be a very flexible tool for ensuring common coding standards and detecting possible code issues early.

- Support for a large variety of programming and markup languages. Even medium-sized projects quickly use a multitude of languages. For example, in addition to the project's primary programming languages, there might be parts written in, e.g., C or JavaScript; the build makes use of Makefiles or shell scripts; the configuration is provided in XML or JSON; infrastructure is configured with Docker and Terraform etc. Codacy allows me to monitor code quality for all these parts of an application in one place.

- Flexible configuration by using configuration files. While you can also configure the tools in the Codacy UI, it allows you to have the rules for code analysis saved in configuration files as part of the analyzed project. That enables the team to easily adjust the rules to their needs while having the configuration versions controlled and documented.

- Integration into your CI workflow: I have used Codacy with both GitHub and Gitlab. The integration into the CI process gives instant feedback to developers and allows the team to ensure that only validated code makes it into the project.

What do you dislike about the product?

Due to many supported languages, the detailed configuration of the rules can require some research. Here Codacy could improve the process by linking to the relevant documentation for the corresponding configuration file.

What problems is the product solving and how is that benefiting you?

Codacy provides static code analysis, which helps set common coding standards for the project team and find potential bugs and security issues early. This results in overall better project quality. In addition, with Codacy, I can use a single tool for my projects instead of relying on various separate tools for each programming language.