Having automation in place is a big win. We do use Code Climate's Quality as you guessed, along other tools you mention. They help the developer get rid of errors and inconsistencies so that the reviewers can really focus on what matters and what only a human can do, i.e. provide contextual feedback on the code.
All these tools are generally trivial to set up in a pipeline and provide great advantages (most of them at little to no cost per month) so that there's really no point in working without them. They offer invaluable help in lowering the margin for errors and increasing speed of delivery.
I would say this is even worth a dedicated post. Thanks for the comment, I really appreciate it.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Hi David, you raise good points.
Having automation in place is a big win. We do use Code Climate's Quality as you guessed, along other tools you mention. They help the developer get rid of errors and inconsistencies so that the reviewers can really focus on what matters and what only a human can do, i.e. provide contextual feedback on the code.
All these tools are generally trivial to set up in a pipeline and provide great advantages (most of them at little to no cost per month) so that there's really no point in working without them. They offer invaluable help in lowering the margin for errors and increasing speed of delivery.
I would say this is even worth a dedicated post. Thanks for the comment, I really appreciate it.