Re:Check-in before code review is an antipattern
by bottled_poe on Saturday January 23, 2016 @09:54PM
(#10961250)
The recommendation seems to be to lock down the code base to the elite few. How about instead, we implement regression testing, employ a competent development team and communicate the software design before coding. Code reviews address the effects, not the cause of the problem.
[ Parent
| on HN ]
Re:Check-in before code review is an antipattern
by madeofpalk on Saturday January 23, 2016 @10:25PM
(#10961328)
We do peer code reviews in pull requests which require at least n people to approve, as well has automated tests which run and report their status back (blocking the PR if tests fail).