Sitemap

Week 5, JavaScript….

3 min readJul 9, 2016

--

After a week of constantly feeling as though I never quite fully understood what was going on, I was looking forward to this week. Although much like last week, week 5 holds a kind of mythical status at Makers: the week when you ‘learn’ JavaScript in a couple of days!

The main aim of the week was to essentially get to grips with JavaScript and a few other related front-end technologies. Our challenge was to create a thermostat app that allows us to set the temperature in our home by clicking on buttons to increase and decrease the “temperature”.

When I first started on my journey to become a developer I tried the Codecademy course for JavaScript and really struggled to get to grips with things in the latter part of the course. I was intrigued to see how I would fair now, having spent the past couple of months with Ruby and learning various development concepts and processes.

The biggest challenge was making the switch from Ruby to JavaScript syntax and getting to grips with a new testing suite, Ruby is a very elegant and forgiving language, JS is quite the opposite. By this point I have switched from Sublime Text to Atom (Atom is awesome!!!) and installed a package that flags any syntax errors in the JS you type, this proved essential in helping me get to grips with those pesky semi-colons.

Get Luke Aveil’s stories in your inbox

Join Medium for free to get updates from this writer.

Another big learning curve was when it came to testing, I have got so used to Rspec that the switch to Jasmine was pretty tough going. I really struggled figuring out what the errors actually meant, as Jasmine doesn’t give you much to work with. It seemed as though this battle was made even harder purely due to the fact that I don’t know enough about JS to be able to make the tests past. One incredibly helpful toolkit to figure out what is going on is the developer console in Chrome, learning to use this proved more helpful than most of the error messages I was getting from Jasmine.

The later part of the challenge involved using jQuery to help make our app interactive and enabled logic to happen in the back-end when a button was clicked or checkbox ticked. I have touched on jQuery before, but this time round it was great to see how it fits into the puzzle with the HTML, CSS and Vanilla JS(pure javascript).

We also had our first introduction to Ajax and API’s, which is a way to bring in data to our web app or change something on the page without having to load a new page. This was really cool to have a play with, but I felt that they are definitely technologies that will be taking up a lot more of my time in order for me to get to grips with.

By the end of the week I had something that resembled a thermostat web app, albeit an unstyled one. JS was fun and I enjoyed diving into the front-end side of things, but do I feel like I learnt JS in a week….obviously not! But I do feel more comfortable with it than I did on Monday morning. I know that it will take me some time yet to feel truly at one with the language in it purest form, but I am keen to dive into a few JS frameworks such as Angular and React to see what I can come up with.

Next week is project week, so I do not think it will be to JS heavy and we will predominately be sticking with Ruby, but who knows what Sam and Mary will throw at us!

--

--

Luke Aveil
Luke Aveil

Written by Luke Aveil

Software Engineer at Converge