Summer of Code, aka Computer says, “No”


So I thought I’d test myself with the Open University’s Summer of Code. Each day, a new problem is set, requiring participants to write a script to solve it. It’s mainly for transitioning second to third years, but as I’ve done a bit of coding in my spare time in the past (using Python) I thought I’d give it a shot.

For my uni course, I’ve been using Sense to do assignment scripts, though not by choice. Sense is a basic programming language using command ‘blocks’, as opposed to having to write out the commands yourself. The OU uses this programming language to teach coding. Sense is ok, but it does ignore certain principles that Python uses, such as the first character in a string in Sense is at position 1, not 0 as it is in Python. It’s also pretty limiting … as I was to find out.

I managed, with a few hiccups, to do the first two day’s tasks using Sense. However, the third task highlighted how basic Sense is. There’s no easy way to convert from letters to the equivalent alphabet numbers. Or rather, not without using a hell of a lot of if-elseif-else blocks that would grind my laptop to a halt. It also didn’t help that it took me half an hour to actually figure out what the problem entailed, as it was written in a rather unclear fashion. After two hours of struggling, and realising I’d left my Python course notes several 100 miles away in Amsterdam, I had to give up. I was rather irked, to say the least. Especially, considering I’d aced the previous two tasks.

Day four wasn’t much better, but by this point, I was getting the impression it was because the questions were overly complicated, rather than the coding itself. If I couldn’t figure out how to do them on paper, how was I expected to do them in code? The tasks were supposed to take two hours to solve, but most of that time was taken up with me going, “WTF??” It also didn’t help that the questions would sometimes have mistakes in their convoluted explanations, making things even less clear.


I gave myself a break from day 5, and tried afresh on day 6. This time, I did progress a little further in answering the question than I had the previous couple of days, but again, I got stymied, so I decided to call quits on the whole thing.

It wasn’t an entirely defeatist move. As it is, I’m also doing a free Open Learn badged course on “English: skills for learning“, which is designed to help “develop the English reading and writing skills needed to succeed” with university work. As I have my final module assignment to do (it’s a doozy), and as one of my next modules will be “English for academic purposes online” I prioritised, and figured out of the two time-sinks, learning how to write a proper assignment was more important than goofing around with unintelligible questions, and contrary scripts.

The past week or so has also made me realise I’ve pretty much forgotten all the Python I’d learnt. Though, in fairness, I haven’t touched the language since 2015. So it looks like I’m going to have to shoe-horn in some refresher learning. Codecademy do a lot of free programming courses, and I’ve already covered jQuery, HTML, CSS and Java with them. However, I did my Python with Coursera (when it used to be a good MOOC provider), which means I can do some Python refresher with Codecademy. I just need to find the time!


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s