From: Ben de Groot <yngwin@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Recruitment process is moving back to quizzes
Date: Sun, 15 Jul 2012 21:45:25 +0800 [thread overview]
Message-ID: <CAB9SyzS2tLnVUQyQH56qzn8VVPfdiZHZa3NxRxx6KDoR-z3p5g@mail.gmail.com> (raw)
In-Reply-To: <CAGfcS_nom=yY+3za7paSpCV1FOejoNzAarAKJ5uJa1+FLCvizA@mail.gmail.com>
On 15 July 2012 21:27, Rich Freeman <rich0@gentoo.org> wrote:
> On Sun, Jul 15, 2012 at 7:56 AM, Ciaran McCreesh
> <ciaran.mccreesh@googlemail.com> wrote:
>> On Sun, 15 Jul 2012 13:15:26 +0800
>> Ben de Groot <yngwin@gentoo.org> wrote:
>>> The first time I did the quizzes, it took me 9 months. After having
>>> been away for a couple of years, I recently returned as Gentoo
>>> dev, and the second time I did the quizzes it took me 3 months.
>>> I've seen others take a long time doing them as well. Davide (pesa),
>>> one of our most valued contributors in the Qt team, took close
>>> to two years I think.
>>
>> If it's taking you that long, you're doing something wrong... The
>> quizzes are pretty easy, and only test the bare minimum of what you
>> should know. They shouldn't take you more than a couple of hours.
>
> I'd be interested in why it was taking so long as well. I took the
> quizzes first when becoming an AT, and later when becoming a dev. The
> level of rigor was much higher of course when becoming a dev - which
> was appropriate. I did struggle because policies were not always
> spelled out, so many of the questions took interaction with my mentor
> to resolve. Sometimes the indirectness of some of the questions was
> frustrating, but it didn't take more than maybe 8 hours in total with
> revisions/etc.
It's not that it takes all that much time. It can be done in say one or two
workdays. But you need to set aside a block of time (and usually two,
one for each of the quizzes, or more if you need to break it up or
iterate over it after feedback) in which you can be relatively
distraction-free and well concentrated. You need to make sure
to check the documentation to find the wanted answers, and word
your answers carefully to be precise and cover all angles.
Since it is a low-urgency and low-fun task, most of us will end up
doing other things on our to-do list, or simply being distracted.
It then gets postponed again and again and again.
--
Cheers,
Ben | yngwin
Gentoo developer
Gentoo Qt project lead, Gentoo Wiki admin
next prev parent reply other threads:[~2012-07-15 13:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-14 9:32 [gentoo-dev] Recruitment process is moving back to quizzes Markos Chandras
2012-07-14 20:46 ` Peter Stuge
2012-07-15 5:15 ` Ben de Groot
2012-07-15 9:39 ` Markos Chandras
2012-07-15 10:11 ` Peter Stuge
2012-07-15 13:21 ` Rich Freeman
2012-07-15 17:23 ` Markos Chandras
2012-07-15 11:56 ` Ciaran McCreesh
2012-07-15 13:27 ` Rich Freeman
2012-07-15 13:45 ` Ben de Groot [this message]
2012-07-15 13:50 ` Ciaran McCreesh
2012-07-15 14:32 ` Peter Stuge
2012-07-15 15:24 ` Rich Freeman
2012-07-15 15:08 ` Ben de Groot
2012-07-15 18:17 ` Denis Dupeyron
2012-07-15 10:15 ` Theo Chatzimichos
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAB9SyzS2tLnVUQyQH56qzn8VVPfdiZHZa3NxRxx6KDoR-z3p5g@mail.gmail.com \
--to=yngwin@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox