Quote:
Originally Posted by vhcook
One technique I use with the students I'm mentoring is to backseat drive. They do all the keyboard/mouse work (we are using Labview, but training is training), and I tell them what to type/click. They ask questions as we go, and it generally works out fairly well. I find that works better than the "I do, you watch" method because it forces me to slow down and explain better and the student gets the hands-on experience to reinforce the information.
|
I second that approach. I haven't had alot of mentoring experience in FIRST yet, but "pair programming" is a work-model my workplace encourages and uses frequently, typically the learner is tasked with 'driving' and the second person thinks about upcoming problems, challenges naming of variables and structure choices, watches for syntax and logic errors etc. (you can also take turns once your closer to the same level, but the watcher has to be familiar, capable, and engaged).
This can be a very effective way to work for any level of programmers, as the driver typically has to focus a significant amount of attention to typing and progressing; the 2nd body can spend some time reflecting on what was just done, or on what needs to be done, and watching for mistakes.
Starting out, your job should be to patiently watch what he's doing, let him ask questions, when you see a mistake or think of a better way to implement, just make a mental note of it and wait until that particular section is completed before pointing things out so that you minimize the interruptions to the writer.