Re:Automated code review for Python, Django, etc.
by ska on Monday April 27, 2015 @11:13AM
(#9446789)
Interesting ... but I still wouldn't call it review. Both linting and review are worth doing, but they achieve very different things. In fact, I often think of linting as a good tool to reduce noise in the review process.
[ Parent
| on HN ]
Re:Automated code review for Python, Django, etc.
by ThePhysicist on Monday April 27, 2015 @11:49AM
(#9447047)
Thanks for the feedback! How would you call it? Static analysis? Linting? Code linting seemed too be a very specific and not widely known term for us while most people seem to know what "code review" means, hence our decision to call it "automated code review".
Re:Automated code review for Python, Django, etc.
by ska on Monday April 27, 2015 @12:27PM
(#9447305)
Well, unless I've missed something, it is by definition static analysis -- so that's probably a good start.
The way I look at it is that every minute you spend discussing a point in a review that could have been caught/corrected by a static tool is a minute wasted. But these tools can't do any of the actual work of the review.
By the way, linting is a fairly well known term with a long history, but it wouldn't surprise me if there are communities that don't know the term.