Better Late Than Never, or New Year’s Resolutions With Qodana
Even before we started to work on Qodana, we knew from our own experience and user interviews that it's hard to add static analysis to a project, which leads people to delay this decision. If you join a project with established code quality procedures, you can just follow the rules. If you start a shiny new project, you can pick any set of rules you want. This option has its pitfalls, but at least you know that your code meets your own standards from the beginning. In contrast, if you join or work for a project where quality gates are not yet part of the process, being pressured to implemen
Early Access Program for Qodana, a New Product That Brings the “Smarts” of JetBrains IDEs Into Your CI Pipeline
JetBrains IDEs are well known for their ability to understand code. They can track declarations, check references and types, and collect possible execution paths. Thanks to all this static analysis, you are able to rename and move things around safely, get appropriate code completion, and get warned with a message saying “hey, this won't run” from the code inspection if you are adding something that won’t work into your code. Having all this while you are working in the editor is extremely helpful, but modern CI-centric workflows require having a reliable quality gate in your build pipeline.