On Mon, Dec 04, 2000 at 10:08:35PM -0500, Bryan C. Warnock wrote: > Be available. Don't give a task, then disappear until its due, accept it, > then disappear again. Answer questions. Check the work. Give feedback. This is very important IMHO; especially for apprentices that really need some ramp-up time. And two-way communication is just important period. Another thing that a master-type person should do is provide a general roadmap of where he is going so that apprentice-types can see how their contribution fits in. Also, this would help apprentices figure out what future tasks they may want to do and if they really want to apprentice in this area. my two cents, -Scott -- Jonathan Scott Duff [EMAIL PROTECTED]
- Perl Apprenticeship Program Bryan C. Warnock
- Re: Perl Apprenticeship Program Nathan Torkington
- Re: Perl Apprenticeship Program Bryan C. Warnock
- Re: Perl Apprenticeship Program Steve Fink
- Re: Perl Apprenticeship Program Bryan C. Warnock
- Re: Perl Apprenticeship Program Jonathan Scott Duff
- Re: Perl Apprenticeship Prog... David Grove
- Re: Perl Apprenticeship ... Bryan C. Warnock
- Re: Perl Apprenticeship Program Uri Guttman
- Re: Perl Apprenticeship Program Jarkko Hietaniemi
- Re: Perl Apprenticeship Program H . Merijn Brand
- Re: Perl Apprenticeship Program Simon Cozens
- Re: Perl Apprenticeship Program David Grove
- Re: Perl Apprenticeship Program Nathan Torkington
- Re: Perl Apprenticeship Program Steve Fink
- Tech documentation (Re: Perl Apprenticesh... Nathan Wiger