News for hackers. Stuff that matters.
Re:Check-in before code review is an antipattern by bitL on Sunday January 24, 2016 @07:13AM (#10962306)
For example code that computes robotic motion via non-linear optimization of non-linear differential equations? Code that computes CFD of Formula 1 car aerodynamics? Code using advanced computer vision allowing autonomous drones? How many of your developers would understand what is going on? Do you think their code review input would be different than a handful of useless comments such as "here is an extra space", "the name of this class has lowercase letters" etc.?

There are no comments on this comment yet.