Re:Check-in before code review is an antipattern
by tyre on Saturday January 23, 2016 @08:41PM
(#10961077)
Note that the author's point about git (the technology) is what it enables users to do.
Teams can still use git or subversion or mercurial and have terrible code review processes, just as they can use Slack or IRC and have terrible communication, or use Ruby, C, Haskell, or ECMAScript 2 and have beautiful or nightmarish code.
Takeaways:
1) Technology is a tool, not an end in itself.
2) People are the hard part. Technology can open the door, but that doesn't mean someone will walk through it.
Teams can still use git or subversion or mercurial and have terrible code review processes, just as they can use Slack or IRC and have terrible communication, or use Ruby, C, Haskell, or ECMAScript 2 and have beautiful or nightmarish code.
Takeaways:
1) Technology is a tool, not an end in itself. 2) People are the hard part. Technology can open the door, but that doesn't mean someone will walk through it.