Error Prone Reviews

CodeClimate Reviews

Error Prone mentions (4)

• How to use Java Records

  A special kind of validation is enforcing that record fields are not null. (Un)fortunately, records do not have any special behavior regarding nullability. You can use tools like NullAway or Error Prone to prevent null in your code in general, or you can add checks to your records:. - Source: dev.to / almost 3 years ago

• Why is `suspend` a language keyword, but @Composable and @Serializable are annotations

  I am all in favour to more third side libraries adding functionalities, like Lombok, Manifold and error prone. As well as smaller projects like this shameless plug and what appears in this list. Source: almost 3 years ago

• Is there a tool to track CVEs for the software that we use?

  While at it you could also point them to static code analyzers such as error_prone, spotbugs and pmd (use all 3 at once - they complement each other in detecting different issues). Source: almost 4 years ago

• Get rid of those boolean function parameters (2015)

  Linters can check for this sort of thing, for example Error Prone[0] has a lint[1] for this. Totally agree this is better to be in the language proper so we don't need this extra tooling. [0]: https://errorprone.info [1]: https://errorprone.info/bugpattern/ParameterName. - Source: Hacker News / about 4 years ago

CodeClimate mentions (17)

• Stop writing code that future devs will hate you for

  CodeClimate quantifies maintainability so teams can’t hand-wave garbage away. - Source: dev.to / 5 days ago

• Essential Resources for Software Technical Debt Management

  Code Climate: Link - Automated code review and quality analysis for codebase health. - Source: dev.to / 3 months ago

• 15 unbreakable laws of software engineering that keep breaking us

  Use tools like SonarQube or CodeClimate to spot the high-risk 20%. Then fix one thing at a time not everything at once. This isn’t Dark Souls. - Source: dev.to / 5 months ago

• Most Effective Approaches for Debugging Applications

  Vishal Shah, Sr. Technical Consultant at WPWeb Infotech, emphasizes this approach, stating, “The first step is to identify the bug by replicating the issue. Understanding the exact conditions that trigger the problem is crucial.” Shah’s workflow includes rigorous testing—unit, integration, and regression tests—followed by peer reviews and staging deployments. Data from GitLab’s 2024 DevSecOps Report supports this,... - Source: dev.to / 5 months ago

• Beyond Bugs: The Hidden Impact of Code Quality (Part 2) 🌟

  - code climate It’s like Sonarqube but doesn’t offer detailed reports and doesn’t support all languages, you can see it from here Https://codeclimate.com/. - Source: dev.to / about 1 year ago