|Re: [ide-dev] Development Process|
Hmmm…but this is _exactly_ the way that everyone at Tasktop and Mylyn does their job! (sound good? see sig line below.. ;D ) Also, many much larger software development enterprises -- there were a number of excellent presentations this year at EclipseCon about that. I'm not saying it always makes me happy ;) -- in fact I sort of have a love-hate relationship with it -- but that's how a review oriented dev cultures operate. I'm actually having difficulty understanding how it would work to have some people be "reviewers" and others be the "coders". Seems ripe for all kinds of socio-pathologies. ;D But yes, it's as big a change in mind set as the other agile practices we've adopted over the years like TDD can be. But there is no reason to adopt Gerrit unless you're seeing the world this way.
On 2013-09-25, at 11:13 AM, Wim Jongman <wim.jongman@xxxxxxxxx> wrote:
> We agree that the "reviewer" must know a lot about the codebase to be productive but I really don't think the two jobs can be done at the same time. It requires a lot of energy to get a large enough patch into the system. It also requires back-and-forth between the contributor and the committer (which can be seen with Gerrit: the committer makes a remark on the code and waits until the contributor responds with a new patch.) This just does not mix with a dedicated programming job.
Miles T. Parker | Tasktop Labs | Tasktop Technologies
skype: milestravisparker | web: http://tasktop.com | blog: http://milesparker.blogspot.com
Committer: Eclipse Mylyn Reviews, R4E, Virgo
Lead: Eclipse Mylyn MFT, AMP
Are you passionate about innovation and excellence and interested in joining our team? Tasktop, voted one of the Best Companies to Work for in British Columbia, is hiring!