I've been tutoring a University level student in Ruby on Rails for a few sessions now. I think it's going quite well. We've been building a medical based application that allows patients to make appointments and doctors to consult and prescribe medication.
It's been refreshing to work on something new.
As I've written about this before, I'll slightly switch up the subject.
Not only has it been refreshing to work on a new project, it's been amazing valuable to me to mentor another person on a new project. When you develop the same project for a long time, it's easy to fall into traps of "this is just how it's done". When you have a new project, it's nice to develop these new skills yourself.
When I develop code, I find nothing more fulfilling than being able to pass my work onto another developer (or even a shiny, new employee) and them being able to understand it. If I could do this with a non-technical person, then Valhalla has been reached.
However, when mentoring, pairing or tutoring, you need to be able to do this on the fly - explaining as you go. This is where I'm currently trying to progress.
Now I've written this entry, I'm reminded once again of the incredibly useful Pair Programming Guide from the team at Tuple.