[teampractices] Code review before writing new code

Wed Jun 10 00:00:25 UTC 2015

 > Exactly. And thus a team prioritizing Bar might continue coding on Bar,
allowing the queue of pending Foo code reviews to pile up.

Bingo!

On Tue, Jun 9, 2015 at 1:55 PM, Kevin Smith <ksmith at wikimedia.org> wrote:

>
> On Tue, Jun 9, 2015 at 1:10 PM, James Douglas <jdouglas at wikimedia.org>
> wrote:
>
>> This prioritization then makes it trivial to decide between reviewing (or
>> fixing, testing, deploying, etc.) feature Foo vs. coding up feature Bar.
>>
>>
> Exactly. And thus a team prioritizing Bar might continue coding on Bar,
> allowing the queue of pending Foo code reviews to pile up.
>
> Kevin
>
>
> _______________________________________________
> teampractices mailing list
> teampractices at lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/teampractices
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.wikimedia.org/pipermail/teampractices/attachments/20150609/cc90c6a8/attachment.html>