1 |
Ciaran McCreesh <ciaran.mccreesh@××××××××××.com> posted |
2 |
20090506223757.106cad31@snowcone, excerpted below, on Wed, 06 May 2009 |
3 |
22:37:57 +0100: |
4 |
|
5 |
> If a question asks "what's wrong with this code?", you know there's |
6 |
> something wrong and you can spend time researching to find out what it |
7 |
> is. But people need to be able to recognise mistakes even when they're |
8 |
> not looking for them, and to know when something's wrong even if they |
9 |
> haven't been told to find the mistake -- being able to do this requires |
10 |
> having a good immediate knowledge of certain parts of the material. |
11 |
|
12 |
You're right, but that's where the history comes in. If the most recent |
13 |
code/ebuilds has/have been crap, needing lots of corrections, etc, they |
14 |
probably need some more pre-dev mentoring. If it's good quality, well, |
15 |
perhaps they're ready to go into apprenticeship, aka actively mentored |
16 |
new dev. After all, the commits from current devs aren't always perfect, |
17 |
as can be seen by the comments on the commit-feed from time to time. |
18 |
|
19 |
Plus, as I said, with a pre-arrangement, it's possible to do email |
20 |
reasonably close to real-time as well, close enough they'd not have time |
21 |
to look it up unless they had /some/ idea what was going on. |
22 |
|
23 |
But it's also possible to structure those questions a bit differently. |
24 |
Provide several samples of code, some of which have problems, some of |
25 |
which don't. Ask them what they'd change if anything, and why. Throw |
26 |
some in from the commit feed which might have minor stuff, plus a couple |
27 |
of known critically wrong examples. Tell them you'll expect a rough |
28 |
"what's wrong" (for the group of several samples) in say 10/20/whatever |
29 |
minutes, and fixes within an hour/2/whatever. There's no reason that |
30 |
can't be done via email, and throwing in some live commit feed action |
31 |
might make it a bit interesting. =:^) |
32 |
|
33 |
-- |
34 |
Duncan - List replies preferred. No HTML msgs. |
35 |
"Every nonfree program has a lord, a master -- |
36 |
and if you use the program, he is your master." Richard Stallman |