Re: [RFH] hackday and GSoC topic suggestions
- From
David Kastrup <dak@gnu.org>
- Date
- Feb 13, 2014, 09:55 UTC
- Message-ID
- <87sirn72w9.fsf@fencepost.gnu.org>
- In-Reply-To
- <CAP8UFD3pqW119xjY0Wci7bJ6UL4ZLsT_vYZJ=zMsnK_7C8-_KQ@mail.gmail.com>
Christian Couder <christian.couder@gmail.com> writes:
Show 11 quoted lines
> On Thu, Feb 13, 2014 at 9:50 AM, Jeff King <peff@peff.net> wrote: > >> I think Google leaves it up to us to decide. I'd be OK with a project >> made of multiple small tasks, as I think it would be an interesting >> experiment. I'd rather not do all of them like that, though. And >> bonus points if they are on a theme that will let the student use the >> ramp-up time from one for another. > > Yeah, a student working on the "git bisect fix/unfixed" feature, could > fix git bisect testing too many merge bases, and if there is still > time work on moving more code from shell to C.
In the context of programming tasks, "if there is still time" is a prime candidate for the successful application of branch prediction.
-- David Kastrup