Skip to main content

What Makes a ‘Machine’?


Defining what it is to be a machine is tricky to say the least. In everyday terms a machine is something man-made that performs an automated function. Computers are often referred to as machines but they are much more than the limited definition above. Perhaps, instead of trying to pin down exactly what a ‘machine’ is in the 21st century, it would be more pertinent to define what a machine is to us.

Isaac Asimov once described machines as ‘the true humanising influence’. In his mind machines would only be used to perform functions and carry out tasks that make life possible, leaving humans more time to do the things that make life worthwhile. Essentially through their ability to perform mundane but necessary actions, machines would allow us to indulge in every part of life outside basic functions, to allow us to enjoy what it is to be human. From a more modern writer’s point of view, machines have gone beyond their initial point of freeing us to taking us over. Stephen King focuses stories on machines gone mad in our increasingly automated world. In his film ‘Maximum Overdrive’, a classic Eighties trashy horror, any machine with moving parts becomes homicidal. Lawnmowers, Walkmans, vending machines and lorries are all affected by a passing comet’s radiation (don’t think about it too hard, it’s not meant to be taken seriously), come to life and start killing people. The only solution (spoiler alert) is to find a place where there are no machines, hide there and wait for the astrological phenomenon to pass. In the film our plucky heroes manage to find a sailing boat and a completely deserted island in the middle of a lake, but in reality finding a place without the presence of even the most basic machine would be practically impossible. In his book ‘Cell’, King uses the ubiquity of the mobile phone to reset the whole of humanity back to its animal instincts. Anyone who doesn’t have a cell phone at the time is soon killed and eaten by those that did. In his view technology and automation are so pervasive that they can plausibly (forgetting the green comet radiation) be used to cause global disasters affecting the whole of humanity. Not a virus or giant tidal waves, but machines we invented and built ourselves.

Conversely, anarchic cartoon South Park showed us that while we might think we don’t need machines, we still want them, especially when it comes to fulfilling mundane, everyday tasks. Characters in a recent episode complained that they were losing their jobs and being replaced by machines, but when given the chance to work as the electronic assistant ‘Alexa’ in the Amazon Dot device, they found the job so demeaning they quit. They realised that adding items to shopping lists and playing songs on demand were jobs that were beneath human beings and left Alexa to it. Who knew that technology would evolve to the point where an episode of South Park would prove a point made by Isaac Asimov nearly fifty years earlier?

Popular culture and plot devices aside, machines, of any kind, were created for a purpose – to make things better. Either to speed up processes, increase yield, reduce workload; to make things safer, quicker or more accurate. When we see a machine in this way, they become a tool to be used, rather than technology to be relied upon. We choose to use them, rather than to not be able to live without them. Rather than our future coming crashing down on us because of our reliance on our own creations, machines will hopefully become assistants to our way of life and give us more time to enjoy it. As Asimov said “It is machines that will do the work that makes life possible and that human beings will do all the other things that make life pleasant and worthwhile.”

Words: Lauren

Originally published: Naked Element

Comments

Popular posts from this blog

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

Catalina-Ant for Tomcat 7

I recently upgraded from Tomcat 6 to Tomcat 7 and all of my Ant deployment scripts stopped working. I eventually worked out why and made the necessary changes, but there doesn’t seem to be a complete description of how to use Catalina-Ant for Tomcat 7 on the web so I thought I'd write one. To start with, make sure Tomcat manager is configured for use by Catalina-Ant. Make sure that manager-script is included in the roles for one of the users in TOMCAT_HOME/conf/tomcat-users.xml . For example: <tomcat-users> <user name="admin" password="s3cr£t" roles="manager-gui, manager-script "/> </tomcat-users> Catalina-Ant for Tomcat 6 was encapsulated within a single JAR file. Catalina-Ant for Tomcat 7 requires four JAR files. One from TOMCAT_HOME/bin : tomcat-juli.jar and three from TOMCAT_HOME/lib: catalina-ant.jar tomcat-coyote.jar tomcat-util.jar There are at least three ways of making the JARs available to Ant: Copy the JARs into th

RESTful Behaviour Guide

I’ve used a lot of existing Representational State Transfer (REST) APIs and have created several of my own. I see a lot of inconsistency, not just between REST APIs but often within a single REST API. I think most developers understand, at a high level, what a REST API is for and how it should work, but lack a detailed understanding. I think the first thing they forget to consider is that REST APIs allow you to identify and manipulate resources on the web. Here I want to look briefly at what a REST API is and offer some advice on how to structure one, how it should behave and what should be considered when building it. I know this isn’t emacs vs vi, but it can be quite contentious. So, as  Barbossa from Pirates of the Caribbean said, this “...is more what you’d call ‘guidelines’ than actual rules.” Resources & Identifiers In their book, Rest in Practice - Hypermedia and Systems Architecture (‎ISBN: 978-0596805821), Jim Webber, Savas Parastatidis and Ian Robinson describe resources