Showing posts with label Course. Show all posts
Showing posts with label Course. Show all posts

Monday, 21 March 2016

Typos

Monday has become a sort of chilled out day, half the time is spent on code reviews and lectures, and the other half learning new terminology and starting on the weekly challenge. It is nice to start the week in a slow way, but at times I just want to power through the new work. 

I was with Chris today, the musician/contract killer (his viola case looks like a sniper case). We spent an age trying to solve a problem that has never happened to us before...rspec not recognising it's own method (i.e. 'feature'). We went up the chain of help. Google failed. Our peers failed. The Alumni Helpers failed. The coaches failed. We were pissed.

In the end, an Alumni Helper, William, decided to look at our code after hours and spot the mistake. It was writing the wrong type of '-' which proved the problem. Sometimes the simplest things are the cause of our problems, but being simple makes them hard to spot. 

Lesson learned: Be cool when stuck.

Also managed to get some free homous and bread, which were left over from a weekend event at Makers.


It was good, but the houmous was very acidic, which I found out later, was a sign the food was off. So I spent the whole day waitin for my stomach to explode.

Also free cookies and possibly free football.

In my opinion, the start of week four has been good!


Sunday, 20 March 2016

MA Week Two Summary

General summary

More Ruby, More TDD

The main challenge this week was to learn more about applying Ruby using a test driven methodology  (rspec) to create a functional piece of software for the London Oyster Card system. The new skill we learned was all about dependency injection (DI). This gave practically everyone headaches and stress!

DI is just a way of reducing coupling (dependency of one object relying on another). Low coupling is the aim of good design, objects knows very little about other objects that it sends messages to. No coupling can never happen, as the object cannot be used by any other object. High coupling is bad, it makes changing one object harder to do, as it will affect the implementation of another object. The lower the coupling the easier it is to change or add to code.

Group session

Had a great group session with Dana (will talk more about her, but she is great) on Tuesday, involving sharing our thoughts so far on our experiences with the course. It was a real eye opener. We had to express our agreement  with the current speaker by showing 'jazz hands'.

We spent around 90 minutes doing this but despite my feelings of regret at not coding, I felt this was a great idea to really connect and learn more about my cohort and myself. There were a lot of emotions being shared around, a few personal stories of overcoming setbacks, a few tears, a few people overcoming their fears to talk in public but most importantly a lot freedom to say what you want and be heard with out being judged or threatened.

I started first, and shared my feelings of feeling stupid, not being good enough, being an imposter, letting my pair partners down. Too my surprise nearly everyone felt the same. Personally, I felt this has held me back a lot in my life, but I am starting to believe that I am good enough and thats alright and all I need to be. Not knowing everything, or feeling stupid or forgetting does not make me rubbish. Class is permanent, form is temporary.

What was surprising was my pair partner for the day, Andrew, felt the same way. Although I felt he was far better at solving the problem, more confident and learning so much more than me. So it was great to hear he felt the same about me and feel that it is alright to be struggling, it is normal. After the session, we had a hug and managed to finish off the task  for the day.  Then a huge group ended up at the bar, with friendships further strengthened.

I feel this group of people I am working with now, are going to be in my life for a long time.

Code review of my weekend challenge

  • Spent the morning with my mentor Jonny going through the weekend challenge (the airport). He was tasked with reviewing my code and helping me improve the style and quality. 
  • Spent time implementing the  changes suggested by my mentor to my code. Spent a lot of time on this, when I felt I should have been doing more pairing on this weeks work. 
Played football for the first time in years

Football is organised for every Monday on the five a side pitch located at the back of the offices. I have not played football in ages, so I knew I would stuggle. I did. I was out of breath after 10 minutes and we still had 50 minutes left to play. Yet despite the struggle ( I am seeing similarites with Makers), I loved it. It was like being back at school on the playground kicking the ball around, kicking it over the fence and having to retrieve it (think most were glad for this as it gave us time to rest).

There was only me, Paul and Si from our cohort, and the rest were seniors and a couple of Alumni playing. It was great game, competitive and friendly. Although we gave up counting goals after 15 minutes, think everyone was too busy gasping for breath to remember.

Big consequence of playing football and walking for commute are that my legs are like jelly and aching like mad!


A visit to the POO DR

As a consequence of a breakout session, we were told to read POO DR by Sandi Metz. This is the bible of good design (SOLID and TDD) with a particular reference to Ruby and bicycle gears. It is a great read, and the topics are well discussed. The big problem is being able to apply them while working through the problems.

I decided on Thursday to stay late, and implement some of the ideas on dependency injection in chapter 3 to my code, to reduce the coupling. Well worth the time spent, code much cleaner.

Pair partners for the week

Monday

My partner was Yasmin (no J), unfortunately we did not have much time together as we had our code reviews and refactoring (improving our code) to get on with. We did sit next to each other and help each other out. We spent around an hour working on the challenge, but did not get very far, although I felt we did some good review of the basics  that were learned last week.

Tuesday

My partner was Andrew and we managed to get through a lot of work together. After the group session, I realised we were at very similar levels and that it was great working together. We had an almighty struggle with problem 12 and I just shouted out in ecstasy when we solved it, which I think disturbed a lot of people (well not many, most had already left).

This was also my first time that I have had to go and see the Alumni Helpers for help. We have been told to see the AH if Google or one of cohort cannot help us. I have always been one to focus on solving problems myself, regardless how long they took. This is a big mistake. I am wasting time, but I guess my ego is involved. So I was glad to admit that I did not know and get some ideas on solving a problem.

Wednesday

My partner was Murilio, from Brazil, and it was a good session partner wise, but we did not exactly do as the question asked and it feels like I have missed out on pushing my learning further.

Worked late at night, trying to understand what was going on with DI.

Thursday

My partner was Junyuan (spelt correctly, which I did not when I was set up GIT, sorry) and it was a tough day. I was so confused by the material, I felt that I did not give as much contribution to the code.

Friday

My partner was Erika. We both finished this week's work, so we decided to redo it again from scratch and see how we got on. Due to being Friday, we finished the day at 4pm when the drinks came out.
Quotes

"You are not your code"

Tuesday, 8 March 2016

MA Week One Summary

What I did?

Monday

  • First day, and it was very easy and relaxed. Only a little bit of coding.
  • Name game. Too long
  • Free breakfast and talk with others
  • Social after
  • paper challenge with Junyan
  • Talk with Dana and Jordan about how to cope with course
Tuesday
  • Had a short introduction about the structure of the course
  • Started working with my pair partner Patrick
  • Worked through the first challenge, creating Boris Bikes, implementing object oriented programming (via Ruby) and Test Driven Development (via Rspec).
Wednesday
  • First stand up in our group with Roi, discussing our wins and struggles from yesterday, and our plans for today.
  • Worked with Kevin, who has a great blog here, decided to start the weekly challenge from scratch due to issues with git and wanting to cement the basics.
  • Joined the meditation group, and did some mindfulness exercises.
Thursday
  • Worked with Harsheet, continued from question 16 out of 22 and used his code as a starting point.
  • Played Ping Pong, and got beat twice. Revenge is on the agenda!!
Friday
  • Worked with Pete, continued from Q20 till the end (see here for my code)
  • After 5 received free drinks and partied with the rest of Makers till midnight.
Weekend
  • Worked on Airport Challenge
  • Went over the Boris Bikes Challenge alone, to cement the work.


What I learned?

  • Big Breakthrough 1: Hammering home that everything in ruby is an object, and ruby syntax is useful but stops the user from seeing this.
  • Big Breakthrough 2: Using mocks in tests, to avoid creating objects from other classes, to help create outputs to help test specific methods.
  • Big Breakthrough 3: Understanding the idea of Behaviour Driven Development, as an overarching methodology to produce software. It really helped see the forest from the trees (implementation and unit tests) 

Challenges and struggles?

  • Struggling with turning user stories into features and feature tests
  • Doing TDD, instead of just normally doing the code first.
  • Feeling dumb and coping with this
  • Working with someone who knew more than I, and feeling like I was not contributing
  • Getting used to working with a Mac. It is the first time I am using one, so I am a bit slow compared to using a unix/windows laptop.
  • Trying to write this blog. It is very hard to find time to write this blog and deal with the course and life. I think I was ambitious in doing it this way, so I will need to do it in a different format.

Success?

  • Finishing off the challenge before the end of the week, despite starting again
  • Using someone elses code base to work from
  • Finishing off the weekend challenge, despite restarting three times
  • Doing meditation twice during the week
  • Working well with my pair partners, and learning lots from each of them
  • Still writing this blog
  • Walking to office and home, 5 times during the week
  • Bringing packed lunch (warm meals with my thermos) everyday, and avoiding eating out and saving money
  • Walked over 10,000 steps twice during the week. 
Other
  • Party on Friday at Makers was great, a great time to really relax and socialise.
  • Going to football next week
  • Spending time with cool, interesting, fun smart and driven people. Nikesh was right, I have found like minded people who I feel I will be friends for a long (whether they will be with me another matter :-( )
  • Really happy with my choice to attend this course, it is really draining and lots to take in. Yet by the end of the weekend I felt that I grasped a lot of new ideas and was able to understand a lot.



Tuesday, 1 March 2016

MA Precourse Week 4

What was done

  • Practised more ruby through completing code wars' katas (not as much as the previous weeks).
  • Met my mentor and did pair programming together.
  • Completed the fizzbuzz kata in ruby using a rspec as the testing framework.
  • Pair programmed with some of my fellow cohorts.

What was learned
  • Learned about "Test Driven Development" (TDD for short).
  • Learned and practised some basic rspec (TDD framework for Ruby) on some basic katas.
  • Learned the basic structure of rspec tests for methods. 
  • Learned about regular expressions.
Struggles
  • When pairing and knowing what was already being explained, but not wanting to sound arrogant. 
  • Pairing in general, very weird not to do my own thing. Although when doing it with Patrick, I just turned my computer off, so we could work together and not be distracted.
  • Writing tests firsts instead of figuring out the method then coding and testing if it works (this is how I approach code wars katas). 
  • Setting up the files, directories, accessing the lib files in rspec.
  • Pairing with Patrick, spent ages on this kata, and two other guys (Tobenna and Paul) both managed to finish it before us and with less code. Despite this, I still felt it was a great learning experience having to explain my ideas and solve problems as a pair.
  • Struggled with using look arounds in regular expressions.
Successes
  • Getting more confident with using regular expressions. I managed to do a quite a few katas on code wars using regex, and I am very happy. I am not perfect, and there are aspects (ie look ahead and look back) which I struggle on. I have got some resources to help me with so I am happy. 
  • Doing some pairing, and not ending up spooning each other (see video below) 
Other
It was him shooting at me at Makers
  • Met my mentor, Jonny, at Makers and spent a couple of hours going through the fizzbuzz rspec pairing tutorial. Jonny was great, and really helpful, he spent so much extra time going through some key ideas on rspec and classes. I feel lucky to have him as a mentor. 
  • While pairing with my mentor, someone decided to rain down on us nerf bullets. Which was a bit of a shock, but all in good fun.
  • Last week of Pre course, and it was a very easy and relaxing week, no weekend challenge (well it was catch up, which meant no work for me as I did everything on time due to not working).
  • Finally going to start, on Monday 29th February, and I am excited and nervous. But not as much as when I started pre course, I have met and worked with a bunch great guys from my cohort at the Ace Hotel, and the chat, via slack, conversations have been fun and helpful. So I can not wait to start working with them.
  • Went to Ace on Tuesday, and we had almost 10 people come in and work. It was great, we had a laugh, helped each other, encouraged each other. Who would have thought coding would be so social. 
  • I have finally been given the code to the Makers office, so no more going through the intercom. I finally feel I a student at Makers.   

Saturday, 27 February 2016

MA Precourse Week 3

What was done

  • More learning and practising ruby coding
  • Finish of all the problems set in Chris Pines Learn to Program
  • More code wars katas

What was learned
  • How to work with tests
  • Practising more Git and command line
  • Understanding more about blocks, procs and lambdas (well not that much of this)
  • Always check the tests first before doing the coding, I would end up using different names which would automatically fail the test otherwise.

Struggles
  • Chapter 14 of Chris Pine. This was all about procs and blocks, which I have always struggled on, but after reading a few tutorials I feel semi confident.
  • Make a better shuffle play list (last exercise in chapter 11). I just could not pass the tests, although I felt my code was good.
  • Need to put issues have on github and get help from my cohort, instead of struggling. I am just spending lots of time on a problem which could be solved with some help. Although, I do believe that the struggle is also helpful, but I will need to get through so much work in the coming months that I need to prioritise my time.
  • I had a persistent cough as a side effect of last week's flu. This stopped me from coming to Ace hotel, as I did not want to pass on my virus and disrupt every one. I am very considerate.

Other
  • Set up a meeting to do some pair programming with my mentor on Monday
  • On Friday, I attended the graduation ceremony for the seniors at Makers. It was great seeing all the  projects, and was impressed by the number of new technologies that they had to learn to get their applications working. Also good to meet and my cohort, and see how much fun and camaraderie between all the students and coaches. I am super excited to get starting full time, but also nervous with all the new stuff that I will have to learn. 
  • Code wars rocks, not only for learning how to solve problems and practise syntax, but also in terms of friendly competition within my cohort (we have a leader board). Currently I am 3rd, although I had an unfair advantage as I did a lot of code wars before my interview at Makers to help me decide if I wanted to move into coding. I must say, code wars is probably the number one activity that has made me want to be a programmer. 
Blog struggles
  • I think I will have to give up doing the whole music section, unless it is really straight forward. It is taking me too long to search for music with some relation to the ideas studied, so will stop putting music unless it is on the first few pages of YouTube search results.
  • Same applies to images and gifs on Google search. Thus my blog is not going to be great to look at, but I will have images of my adventures in Makers which should make up for it.

Tuesday, 16 February 2016

MA Precourse Week 2

This week has been rubbish. Sunday evening I started to feel ill, and ended up with the flu. I have been stuck in bed for 3 days with very little work done.

What was done


What was learned
  • Basic ideas and implementation of ruby (ie strings, variables, methods, control flow, hashes, arrays, blocs etc) by going through Ruby Kickstart and doing the associated exercises.
  • Never struggle for longer than 30 minutes
  • If struggling, take a break and come back to it later or when inspiration strikes.
Struggles
  • I have been sick with the flu for the whole week, so trying to code has been difficult. Glad that I did not manage to get behind and keep up with my peers.
  • Seriously need a tidy, clean and orderly environment to be able to concentrate with coding.
  • Doing katas (programming problems) with procs, blocks and lambdas. Still don't understand these ideas, but they are really useful so will need to spend more time reading up on them.

Success
  • Managed to finish off all the problems set for this week, despite being ill. 
  • Improve my code wars score. I am second in my cohort, but top place is over 60 points ahead so I doubt I will have time to overtake him. I know it is not a competition, but it is really cool trying to improve my record while trying different problems.

Other
  • Our cohort was assigned mentors, mine is Jonny, and we spoke over slack. Very helpful guy and looking forward to working with him.
  • Slack is brilliant, everyone is helping each other, learning new and different ways of solving problems. Everyone needs to get on this.

Need to do
  • Get comfortable using regular expressions
  • Meet up with the guys during the week
  • Learn more about procs, blocks, and lambdas and do related katas on codewars
  • Make a start on Ruby Koans and Ruby Monk 
  • Meet my cohort and more people from MA at the graduation ceremony. I feel like I have known my cohort for ages (only just over 2 weeks) so should be great to meet most of the guys again. This event will be really exciting, as we will witness the final projects  being presented and will either be inspiring or nerve wrecking as this will be us in another 12 weeks!!!
Life goals


Sunday, 7 February 2016

MA Precourse Week 1


What was learned

  • Introductory material from MA
  • Command line interface (CLI)
  • GIT and GITHUB
  • Working with others to learn from and help solve problems
  • Improving problem solving in programming

Activities

  • Communicating using Slack
  • Work through command line tutorials (See links here) and Git tutorials (See links here)
  • Setting up my computer with required software (Sublime Text, Ruby, Git etc)
  • Went through Git immersion tutorial (still need to finish)
  • Finished the challenges for Git and CLI
  • Write up reflections for the week for the coaches at MA to help me with my learning (sort of like this blog)
  • Pracitised my typing skills during the week
  • Worked on some ruby kickstarter, code wars and Chris Pine
  • Wrote flash cards for key commands for GIT and CLI (use Anki)
  • Spent Thursday at Ace Hotel, Shoreditch with Gaby, Kevin, Tobenu and Patrick. Went through command line and Git immersion together. 
  • Spent Friday at Forge, just across from the Ace Hotel. Although no one came by, I got loads done and using a table is far better than a sofa. 

Struggles

  • I got stuck for ages on a couple of the questions on this weeks challenge on comand line, one I managed to solve (forgot speech marks, duh!) and the other was a unix problem (solved using nitrous command line). Big thanks to Adil!!!
Most of these commits were for one question!!!

  • Really need to be more strict with my breaks. I just plough through and it is not great. I end up feeling really tired and straining my eyes.
  • Got to level 14 on git immersion, and had to restart as I changed the .gitconfig in my folder instead of doing it for my profile...annoying, but at least I did not have to restart level 50!!
  • When going to cafes or hotels to work in, need to do so early in the day, as the lighting is crap and really tires me out.
  • Can be hard learning in public venues, lots of background noise which is distracting, need to bring some headphones and play some pink noise to drown it out. Click on the video below if you want to be bored...

Successes

  • Finished most of this week's work early, so I got started on Chris Pine and Kickstarter.
  • Working with some guys during the week was great, everyone was friendly and we all helped each other when stuck. Special shout out to Tobenna for looking after our stuff when going out for breaks.
  • Good at switching to different topics to keep fresh (should stick to 30 minutes rule). For example, not doing one tutorial on command line all day, but doing something else.
  • Avoiding spending all my time on one topic and mix up topics studied through the day (interleaving effect - good for learning)
  • Keeping a log of what I need to do for each week and what needs to be completed.
  • Helping guys on slack.

Other stuff

  • Before the start of MA, I already started to play with Git and started to push some code to Github. This is the basic stuff, but there is so much more to Git than meets the eye (ie Git immersion).
  • I have used command line before (not to the extent used in MA), the first computer I used was DOS based so everything was done on the command line, no windows and monochrome (yellow) colour.
  • The pre course website is fantastic and is really helping me organise my activities for the week.
  • Everyone is really helpful

Need to do:

  • Pair program on ruby problems
  • Memorise commands for tasks in CLI and GIT
  • Stop using my mouse and use keyboard commands instead. Also use CLI to manipulate files and folders instead of "My Documents". 
  • Read some books on ruby.
  • Set a time limit for my work, so I can have regular breaks.
  • Finish Git immersion course
Here are some more videos relating to this week's content (hard to find anything good that had some link to the GIT or CLI):



Tuesday, 2 February 2016

MA Pre Course Day 1

Monday was the official start day of the pre course for the February 2016 cohort!!!

In a nutshell, it was just a get together of the members of the cohort getting to know each other and what to expect during the next four weeks.

Highlights:
  • Name game and introducing our partners after talking for 5 minutes to the rest of the group
  • We all had a laugh when trying to communicate with the rest of the cohort online.
  • It was a quick affair and went to the local bar to socialise with everyone.
  • Everyone was really cool and friendly, even had a chat with a couple of senior guys who were imparting their wisdom.
As this was the first day, I have done the following:
  • Worked on a couple of tutorials for the command line interface (CLI)
  • Practised my shortcuts for Sublime Text
  • Practised typing
  • Uploaded some code to Github
  • Read some blogs of MA students
Aims:
  • Meet up with some of the guys to do some pair programming and learn off each other
  • Get into a daily routine, get as much work done, exercise, meditate, sleep, regular breaks from the computer screen, etc.
Here are the anthems of the day (do not know how long I will do these music interludes):