3 ms·
That's a good list but don't mix being independent and being alone. Beginners shouldn't be left alone for any sort of feature even if they are competent.The fi
by remify 8y ago
That's a good list but don't mix being independent and being alone.
Beginners shouldn't be left alone for any sort of feature even if they are competent.The first couples of months you need a lot of feedback (more then a stand up every day). I'd say pair programming is the way to go.
- NicoJuicy 8y agoHe mentioned a new software job. An onboarding "event" should more or less happen existing software /architecture. This wasn't mentioned. Pair programming is slow. You want everyone to be B+, while they become C's. I keep the A+'s and migrate the F's to testing or something else. I never excluded meetings anywhere. I suppose the normal flow of analysis and explaining inner workings/features is still possible, I hadn't banned them. Just mentioned the stand-up as a recurring event for normal development days