Skip to main content

JavaScripting across the universe

I’ve been using JavaScript reluctantly on and off for years. I’m currently working on a project that is highly dependant on JQuery based, handwritten JavaScript. Just as Rupert described in this workshop, I am one of the world’s copy-and-paste JavaScripters, so I thought it was about time I looked at it more closely to see what I was missing. I recently took on an apprentice who also needed to learn JavaScript, so a Norfolk Developers workshop was ideal for us.

We all know there’s a software development skills shortage nationally and very much so locally and this is something Norfolk Developers is trying to do something about by introducing a series of introductory workshops aimed at those with little or no experience. Initially Norfolk Developers will be concentrating on web development skills such as HTML & CSS, JavaScript and JQuery. There are also plans for introductory workshops for iOS and Android mobile development. The group will also continue to cater for the more experienced developers with their regular series of intermediate and advanced workshops.

We all know JavaScript is evil, right? Yes, but it’s a necessary evil and there are reasons it’s evil. This was very well explained by Rupert Redington at Norfolk Developers’ JavaScript Starter Kit, beginners full day workshop. It was created in two weeks and suffered a little because of that, but we are where we are.


What was really great about the workshop for me was that I was able to learn and understand the details of the language I had missed before, such as the different ways things are compared for equality in the language.

After an interesting and in depth introduction to the language Rupert introduced us to NodeSchool, which is a series of tasks designed to help you learn and write JavaScript one step at a time in a rewarding way. You write the code to solve a problem, run the test and it tells you whether you have it right or not. I could have done that for hours!

In the afternoon we brought together a lot of what we had learnt in the morning to write a simple one page web application which used our browser’s API (Application Programming Interface) to find our current location and an external API to look up where the nearest public toilets were to us. It was fantastic to see what we’d learnt solving a real world problem.

Rupert will be back in the summer running an updated beginners JavaScript workshop.

Comments

Popular posts from this blog

It's great to be back at the ACCU Conference 2025!

Last week I was back at the ACCU Conference in Bristol, for the first time since I gave an opening keynote in 2019 . In March 2020, COVID hit the UK and I got out of the habit of attending and speaking at conferences. Plus the ACCU Conference, and the organisation in general, took a big step back towards C++ and that hasn’t been relevant to me for nearly two decades. It’s taken until now, 2025 for me to want to talk again, and I was really pleased to be accepted for the ACCU Conference again. It was just a 20 minute session and I only attended for the day I was speaking. There was enough varied content for it to be interesting to me and I’m hoping to be back for the full conference next year. I really enjoyed attending and it was great to catch up with people I hadn’t seen for years. I felt re-engaged and particularly liked being asked if I’d been to nor(DEV):con . Learning to stop writing code (and why you won't miss it) Daisy Hollman I should have read the summary of the openin...

I, Robot

The Foundation series has been my go to for a good, enjoyable read over the last two years, so naturally I moved on to Asimov’s Robot series afterwards. However, the short stories in I, Robot were mostly a disappointment. They feel self indulgent, with too much philosophy and science, Asimov showing off, and not enough story. The most enjoyable moments come from the stories featuring Gregory Powell and Mike Donovan. Their banter and the relationship between them provide some much needed amusement and were easily the highlight of the book for me. However, it did give me food for thought for the current potential issues with the rapid development of AI at the moment, and the many concerns around safety. I wonder if all we need is: An AI may not injure a human being or, through inaction, allow a human being to come to harm. An AI must obey the orders given it by human beings except where such orders would conflict with the First Law. An AI must protect its own existence as long as such p...

Write Your Own Load Balancer: A worked Example

I was out walking with a techie friend of mine I’d not seen for a while and he asked me if I’d written anything recently. I hadn’t, other than an article on data sharing a few months before and I realised I was missing it. Well, not the writing itself, but the end result. In the last few weeks, another friend of mine, John Cricket , has been setting weekly code challenges via linkedin and his new website, https://codingchallenges.fyi/ . They were all quite interesting, but one in particular on writing load balancers appealed, so I thought I’d kill two birds with one stone and write up a worked example. You’ll find my worked example below. The challenge itself is italics and voice is that of John Crickets. The Coding Challenge https://codingchallenges.fyi/challenges/challenge-load-balancer/ Write Your Own Load Balancer This challenge is to build your own application layer load balancer. A load balancer sits in front of a group of servers and routes client requests across all of the serv...