3 ms·
You can always start with linters and make them part of your CI acceptance. You can go quite far with this eg in C# enforce code contracts to ensure no rouge nu
by quickthrower2 7y ago
You can always start with linters and make them part of your CI acceptance. You can go quite far with this eg in C# enforce code contracts to ensure no rouge nulls. Or keep it light and just check for basic things.
This doesn’t automate the review but saves discussing minor things in the reviews.
- tmm84 7y agoI agree with using linters that are very strict. They save a lot of time by making sure things are uniform. Most of the time I need to fix stuff in a codebase is because the style was all over the place and if the style was consistent then refactoring or making the code simpler wouldn't have been much of a problem.