This week, we saw more advances in the world of Rails for Matthew. Nick is now our “client”, spelling out his ideas for an internal application the company needs in order to track project schedules. Monday was dedicated to having the meeting with Nick and then building the first few pieces of the application. Matthew had a working prototype to demo by the end of the day.
On Tuesday, I had him watch a couple more Railscasts in order to follow the Nested Model Form example for the two models that have a parent/child relationship. Again, at the end of the day, he had a working demo of the changes he’d made, really blowing us away. We did a code review at the end of the day and aside from a few formatting issues, I thought he did absolutely great! This morning, I caught just one more issue with his understanding of the Rails convention of RESTful resources, but it was not a big deal at all to make the change and then explain the differences.
For today, we went back over the code and how to go about testing it. Yes, normally, you test first, but because we’re leaving the codebase up to Matthew alone (for the most part), I decided I would use testing-after-the-fact to show him how such tests can be written. Since the production code is already written, we made sure to take the necessary steps to force the tests to fail. It’s important to see a test fail so that you know it passes for the right reasons.
Matthew demo’d his first iteration of the application today, for the end of “Sprint 1” and the end of his third week as a Neoteric Apprentice. Holy moly! He continues to impress us! And that’s it for this week. For homework, he’s going to study up on the Rails Asset Pipeline because he’ll be working mostly in the front-end on the following iterations of the application. That’s where Nic Aitch will step in and show him the ropes!
Well done, Matthew, and we’ll see you next week!
Have a comment or question? Send us a note. It won't be shown here and email isn't required, unless you'd like a