Day 3 — week 1
Today was really great. We started the day with a stand-up (a meeting where everyone stands up to keep it short) and talked about what people learned yesterday, what they were gonna focus on today and what they struggled with. We are going to have these meetings every morning, as a way of reflecting on the day prior, and to get a feeling of where everyone is. It’s also a way for our coach to figure out if there are any subjects that most of us struggle with, so he can focus on explaining it better and maybe do a workshop on it.
Anyway, after the meeting my pair partner of today and I went on with the Boris Bike challenge. I was 5 exercises ahead of him, so today it was me who had to go back and do those again (we always start from where the person who’s behind left off), and it turned out to be really great. Being forced to go through some of the material again made me realise that I actually hadn’t understood certain things completely, and it was a great way to find out about that by having to explain it to my pair partner. We had a really great flow, and coded the whole day only interrupted by meditation at 2pm and yoga at 5pm.
After yoga I went to Mile End Stadium to run track with TrackEast. It’s something that I really enjoy, but I decided today that I’m not gonna go anymore until after I finish studying at Makers. The trip there, warmup, actual training, cool down and my commute back home takes more than 3 hours — and I want to prioritise that time to study while I’m enrolled in this course. Coding is my number one focus right now, and I’m totally fine with that. I can run track in 3 months!
What I learned today:
- Why limiting scope and privatising as much as possible is super important in OOP
- to use
?after a statement followed by one condition if true, followed by
:and then another condition if false. Just like this
@bikes[-1].working? == false ? nil : @bikes.popwhich in our program is saying “if the
.working?method on the last element of the
nil, otherwise remove it
- That you can make a class or method in pry and edit it using
editfollowed by the name of the object
- That it’s smart to have your feature tests in a separate document for easy access
- To better understand Rspec error messages
What I want to focus on tomorrow:
- More rspec — I feel like this is gonna be a main priority throughout the course as it’s super important, but really hard.
- Figure out the purpose of using doubles in testing (where we left off today)
- I want to see if I can get time to read the first chapter of Practical Object-Oriented Design in Ruby even though we have a social with beer and wine
What I struggle with:
That’s all for today!