Week 1: Weekend challenge

Our first weekend challenge is writing an airport programme. The airport can make planes land and take off, when the weather is nice – but be careful when it’s stormy.

The whole week was all about learning Rspec and the test-driven approach. I have to admit, I’m not in love with Rspec. Not at all.

[rant start] I find it still very frustrating to spend ages on figuring out how to write a test, if I can write the actual method for my programme a lot quicker. I just trust in the system that is Maker’s to know best, and will hopefully get used to it (so I’ve been told by seniors – they actually had some kind words for Rspec … these won’t be found in the Feb cohort atm…).

Another thing, which doesn’t make writing the specs any easier, is that Rspec had the brilliant idea to update their syntax. While the new syntax is probably the latest jazz in writing specs, it is SO annoying because much of the resource material is now outdated. And their is so. much. outdated. stuff! Even seemingly great resources like code school, who made a rap song about Rspec, have now outdated should-syntax. An up-to-date resource is, apart from official docs, is betterspecs.org which has been suggested during on of our stand ups. [/rant end]

That felt good, sorrynotsorry about that.

Back to the actual topic: Weekend challenge! It is exactly that, a challenge! Naturally we can use a lot from material we covered during the week, but have to adapt it accordingly. I still find that I often overcomplicate things, and try to do more that I actually should or test things, that don’t need to be tested.. and there is this one test, I shouldn’t pass but get a green…oops. Still working on that. 😛

Tomorrow I think, we’ll get together with our seniors and discuss the code we’re written for the weekend challenge. We’ll see how that goes.

✈️

Leave a Reply

Your email address will not be published. Required fields are marked *