PreCourse Week 1 – Summary

All the Maker’s students have to fill out a weekly learning process. Throughout the course, the students use the agile methodology to reflect on their progress and their work in general.

So here’s what I’ve taken from the first week of Maker’s precourse!

Most Important Things I Learned:

  • It’s okay not to be the first to finish every exercise (note: especially if you’re working full time)
  • The command line can be understood! (even if it looks odd at first)

Things I Struggled With The Most:

  • From the material – understanding grep and regex
  • In general – working full time and doing all the prep work

Changes I Plan to Make Next Week:

  • Strict learning schedule (see you in 15 weeks, friends!)
  • Doing the optional exercises which I haven’t done yet
  • Get going with Ruby!

Other Experiences This Week:

  • Using Slack (our communication channel) makes me feel part of the community despite being unable to attend day-time learning groups
  • If you want to pass the challenges, you need to follow the instructions to the letter – things like different file names cause the tests to fail

Bottom line:

We covered a lot of material in the first week and looking back, it’s crazy to think it’s only been a week of studying – 6 days to be fair, since on the first day we didn’t get any material! I’m definitely enjoying it so far, despite my head hitting my desk occasionally. 🙂

Precourse week #2 here I come!

Source: http://guh-gifgarden.tumblr.com/post/49104576486

Your wish is my command (line)…

During the first week of the precourse, we’re focussing on learning about the command line and version control.

For the past few months I’ve been doing a series of courses on the website coursera.org about responsive web design. The courses talk about programming languages such as HTML, CSS and Javascript, and also uses the Meteor framework which runs on MongoDB. So during the courses I’ve learnt the mere basics about using the terminal/command line (‘cd’, ‘mkdir’, how to ‘add’/’remove’ packages to our meteor projects, view the db etc). As the course teaches quite a broad spectrum, they didn’t really go into the whys and hows of the command line, so I’m pleased to actually really focus on it now in the precourse.

I think the hardest thing for me is to see using the commands in the terminal like any other programming language. Just like in JS, we’ve got functions that take arguments, we can run them and we can get something in return, change something, etc. I know the terminal can do more, but me and my brain are taking one step at a time!

My favourite command is obviously ‘man’ – a saviour!

One of my fellow maker’s students has also told me he’s done the command line track on codecadamy.com. After I’ll finished the Maker’s material on the command line, I want to do this 2-hour track as well – having different types of learning input will definitely be helpful! (I believe they have also one on git – wahay 🙂 )