Re:Check-in before code review is an antipattern
by bitL on Saturday January 23, 2016 @10:56PM
(#10961396)
Unfortunately, the coworkers might not be intellectually capable of understanding it at all, not even in infinite time :-( I understand this could be a management nightmare, but some things are just "given from above" and you can either turn a blind eye on them and lose the race, or use them for the benefit of your people. I would choose the latter even if I can't control it.
[ Parent
| on HN ]
Re:Check-in before code review is an antipattern
by 13of40 on Saturday January 23, 2016 @11:47PM
(#10961506)
Huh - can you share a piece of source code that the average developer wouldn't be intellectually capable of understanding, not even in infinite time? Or point to one in the open source corpus?
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.?