Skip to content
chastell edited this page Dec 21, 2011 · 41 revisions

This is the index page for reports about actual mentoring sessions.

Mentors, check the Instructions for mentors page for how to add your reports here.

afcapel

19-april-2011: review puzzle node #1 transcript

aguids

08-August-2011: Talk about tests and TDD from Puzzlenode problems. (transcript)

13-May-2011: P2PU - Working with recursive methods (transcript)

21-April-2011: Reviewing Puzzlenode #3 and #4. Improving code organization, algorithms and making better use of Ruby idioms. (transcript)

andev

30-April-2011: Reviewing Puzzlenode #4. Working out a better algorithm to find the sequence of active lasers. Touched on code organization issues, but tentatively scheduled another session to go more into that aspect. (transcript)

11-Aug-2011: Reviewing Turtle Track puzzle (transcript)

15-Aug-2011: Reviewing Wired Up puzzle and detailed walk-through of two example solutions. Demonstrating the use of recursion and why that is a good approach in this particular puzzle. (transcript)

chastell

21-Dec-2011: Reviewed the Chess Validator and Six Degrees of Separation puzzles. The solutions were architectually sound, so mostly concentrated on Javaisms vs Rubyisms (in design and in code). (transcript)

ericgj

18-Dec-2011: Sherin's Chess Validator. Refactoring so pieces don't need to know about board geometry; dealing with potential moves, with and without deep cloning the board. (transcript).

14-Dec-2011: Arun's Chess Validator and Poor Man's Forth submissions. (transcript).

4-Sep-2011: Reviewing Brandon's (thenovices) Puzzlenode #7 (Blue Hawaii). Reworking a procedural solution. (transcript/stypi).

14-Aug-2011: Reviewing johnnymugs' Puzzlenode #12, from MU admissions. Reworking a procedural solution. (transcript/Etherpad).

2-Aug-2011: Reviewing robertodecurnex's Puzzlenode #11 and #12, and briefly #10, from MU admissions. Encapsulating procedural code, user interface tips for puzzlenode problems, using Array#cycle. (transcript).

29-June-2011: Reviewing jedschneider's Blue Hawaii and Steganography, and ideas for his core course project. Extend'ing objects as an alternative to subclassing, using Comparable, and lots of little rubyisms. (transcript)

17-June-2011: Reviewing yankoff's Steganography (Puzzlenode #6). We started moving procedural code into an class, running into some useful dead ends along the way. Also suggested using bitwise operators instead of string array. (transcript and etherpad)

26-April-2011: Reviewing Anderson's Puzzlenode #2 and #3. Looking at existing algorithms, more idiomatic/less procedural code, tips on code organization. (transcript).

19-April-2011: Reviewing Srini's PuzzleNode #1 plus briefly #3 and #4. Srini is a student in the May core course. P1 requirements, object orientation vs procedures + global variables, object orientation vs primitive obsession, code readability. (transcript)

ignacy

28-April-2011: Reviewing puzzlenode solutions; module vs. class; (transcript)

semmons99

For all mentoring sessions after 2011-07-29, see our issues log.

29-July-2011: Reviewing PuzzleNode #9 and #12 from MU admissions. (transcript)

29-July-2011: Reviewing PuzzleNode #10 and #11 from MU admissions. (transcript)

29-July-2011: Reviewing PuzzleNode #10 and #12 from MU admissions. (transcript)

23-June-2011: PuzzleNode #6 & #7 with RbMU Application. (transcript)

16-June-2011: PuzzleNode #7 Blue Hawaii. (transcript)

06-June-2011: Designing an public API and Translation Engine API for Threepio. (transcript)

02-June-2011: Reviewing RbMU Individual Project and planning a new Gem. ([transcript](http://university.rubymendicant.com/chat/messages?channel=%23rmu-study-hall-1&topic=02-June-2011+hgass+with semmons99&full_log=true))

26-May-2011: Reviewing RbMU submission. Writing idiomatic code, being clear versus being clever. (transcript)

21-April-2011: Reviewing PuzzleNode #2 and #3. Researching algorithms, performance and object-orientation. (transcript)

19-April-2011: Reviewing PuzzleNode #1 and #4. Making code less procedural and more object-oriented. (transcript)