Working with a Mentor

As part of gSchool, we were assigned a mentor last week.

I had the good fortune of getting a mentor who works in the same building as our classes, so I was able to meet her in person (thanks to @QuillyT, who hunted me down to introduce us!). Our first official mentoring session will start on Monday.

My mentor offered to meet over the weekend, but I am always concerned about taking up someone's time so I said I didn't want to make her do the drive and instead offered to make a list of questions that came up while I was reading over the weekend. 

Interestingly, later that day in the weekly one-on-one's I asked Jeff(@j3) for his advice for utilizing a mentor's time appropriately and he said to let them define what asking too much was. Not to hesitate to take what was offered or be afraid to ask too many questions. 

He also said that those who benefited from a mentor the most in the last class were those who set up regular meetings - like saying we will meet for two hours weekly on Mondays instead of 'we'll grab lunch whenever'. This makes it something that's easy to schedule for them, and consistent for us. 

And finally, he advised to give a mentor something specific. Instead of giving them a github repository and asking how it looks, instead ask where they would have improved the tests. He mentioned the old adage (which I am likely misquoting) that if you give a programmer 6 pages of code they'll say it 'looks great'  but if you give them six lines, they'll give you six improvements.


My first email/question to my mentor is below.

And here was her most excellent response

 The neat thing is that this is the sort of question that's too vague to ask somewhere like Stackoverflow and maybe a little too specific to the dorky things I'm doing to ask in class.  

Question 1
Right now I’m working on a silly game for ex45 of the Ruby the Hard Way exercises.
(It’s a spin off of the Bill Braskey sketches on SNL - so that’s kind of embarassing!)
I was trying to test drive development - and I stubbed out all of the gets statements so that they wouldn't futz up the tests. But Ive gotten to the point that I'm testing out gameplay and put the statements back in.
How would you approach moving forward? Is there a way to test gets methods? (assert_output?)
Is this a common issue, or am I not seeing the forest for the trees and using gets commands are only really used this often when you’re making silly command line games?
Should I scrap my tests in order to finish the game - or spend the time to go back and stub out the ‘gets’ methods?

See response here