> On Oct 27, 2017, at 1:48 PM, Vasco Alexandre da Silva Costa
> <vasco.co...@gmail.com> wrote:
>
> 75 tasks? That's nuts!
> What was the requirement in previous years?
100.
Note that’s usually nowhere near adequate…that’s just for the opening week. If
we’re responsive and tasks are well defined, the kids can clear those out fast
and complete considerably more. We cleared 383 in 2014/2015 (slide 3):
https://drive.google.com/open?id=1_hpa0tYPKRtRAjl2blcLL_-c94CYMkY2W0hcJMsaihU
<https://drive.google.com/open?id=1_hpa0tYPKRtRAjl2blcLL_-c94CYMkY2W0hcJMsaihU>
Given there are more orgs, I wouldn’t necessarily expect that again, but it’s
not inconceivable. The Zulip guys, for example, were very well set up and
cleared >700 last year.
When thinking about tasks, it’s important we keep a consistent time and
complexity rubric in mind. Aim for 2 hours.
That is, we should define tasks that take an “average” experienced developer
with an environment and tools already set up about 2 hours of work (give or
take an hour). For big sets of nearly identical tasks, it’s good to try one to
make sure it’s not that far off the mark. Scoped that way, it’ll usually end
up taking the participants anywhere from an hour to a few days to complete most
tasks and they will gobble them up like candy as they get experienced.
Cheers!
Sean
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
BRL-CAD Developer mailing list
brlcad-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/brlcad-devel
