Makers Academy – Week 2

Week 2 largely consisted of working through Ruby exercises and doing various challenges to exercise our abstract minds and get us thinking like coders. One challenge, the FizzBuzz kata was very interesting. It was tough for someone who has just started programming to figure out all the possible ways to make the code achieve what we wanted it to. Makers Academy┬ámakes sure that all it’s graduates are ingrained with the principles of TDD (Test Driven Development) this is basically writing down what each element of the code is meant to achieve on a very deep level so that you can be sure that when you edit things in future that all the other elements remain correct. It is important for laying the foundations for code so that a team or even a different team can come back to the code and edit it with ease, rather than having to figure out for themselves what every element of the code does.

Week 2 being over, I must say things are looking up. I am aware and feel like I know more so much more than I did last week and I am looking forward to learning more next week.

Makers Academy – Day 9 – Tri Programming

In contrast to last week and my assessment of that week, I am beginning to get a sense that I can really achieve at Makers Academy. We are actually doing challenges and building things to simple specifications. It is really challenging and interesting. I as a pair (or a tri) with two of the other “Makers” have attempted a Roman Numerals challenge which spits out roman numerals when you enter a series of numbers up until 4999. It is interesting to work through the problem with the others and use all of our knowledge to successfully complete the challenge. It is amazing what conclusions a collective comes to that perhaps an individual wouldn’t have. I am really starting to enjoy the challenge of learning to code and to adapt to thinking like a coder. I really feel like Tri-ing now! (oh dear!)

It was a bloody question mark?!

The most frustrating thing about learning to code and probably coding in general are the stupid errors! The missing question marks or commas instead of full stops hidden away in the code. It is the most frustrating thing I have yet found in my 6 days here at Makers Academy. Staring for hours at the screen trying to work out the really complicated issue with the code that is causing everything to break every time but no it is the bloody question mark!

Ok so I had a little bit of a rant. :) This can be quite frustrating sometimes. However it turns out I got what I wanted this week. Straight away we went in to programming actual things that do things over and above printing text to the console. It would be fantastic if it wasn’t for the bloody question mark!