The wording is definitely a bit awkward. (disclosure: I pitched the news announcement to TC so it's kinda my fault). I always find hard to explain technical de

The wording is definitely a bit awkward. (disclosure: I pitched the news announcement to TC so it's kinda my fault). I always find hard to explain technical debt and connect it to code reviews in a concise manner. I believe you're 100% correct. Coming from a .NET world, you are definitely well served by great tools. Our main selling point with Codacy is that there's a higher value to static analysis tools when they are not only integrated in the collaboration workflow (i.e. Github, Bitbucket, Gitlab, etc) but also integrated with other tools. How does one discover quickly what is the code quality impact of a commit/pull request done by a team member? How about whether a pull request is ready for merge? That's what we're doing essentially.