The basics

Description

The robots are here! No more work! It’s great! Is it great?! Wait! You feel apathetic and unproductive! You miss clicking buttons! You miss waiting for progress bars! You miss checkboxes! You miss work! But it’s going to be okay! Use this handy application and it is as if you were doing work!

History

It is as if you were doing work had been around for a long time before I really managed to start working on it properly. I actually documented the original moment that sparked that game in a blog post titled Close analysis of having a game idea – basically I was watching Rilla resizing an image while working on a project and suddenly felt like it would be amazing to have a game entirely premised on totally conventional operations with traditional user-interfaces. From there it became the idea of a WarioWare-esque game where you would complete simple interface operations under time pressure (I will likely return to this) with various ideas for layering on some kind of meta-narrative, or AI-twist, or something to make it more ‘spectacular’.

After a couple of months with it on the back-burner, I came back to the game thinking mostly in terms of technologies. Specifically, I was teaching a web development course at university and started thinking it would be interesting to build a game using a kind of standard-issue user-interface library like jQuery as opposed to building it with a game engine. It felt like there was something appropriate about using tools that actually fit in with the nature of the game as interface-oriented. So at that point I started nailing down what I’d actually be able to implement with jQuery UI’s tools (e.g. checkboxes, radio buttons, buttons, progress bars, etc.).

At a certain point while working on the actual underlying framework I tried to name the game and realised it could actually serve as a kind of sequel to It is as if you were playing chess, hence: It is as if you were doing work. The title gave some more structure to what the game was meant to be about. Rather than being WarioWare-style zany fun with interface elements, it now needed to fit into the It is as if idea of a performative game that enables you to simulate an activity.

Making the game a sequel briefly led me down a path of trying to make an incredibly abstract version where there was little to no actual language and the texts were represented with unicode block characters instead. The UI was styled in a similar way to It is as if you were playing chess with clean white lines on a dark grey. It actually looked pretty good, but it became so abstract that it was less and less clear that the was about anything. When playing around with the interface elements I had a feeling of detachment, rather than the sense of simulating work.

I had a break-through on this front in New Zealand when I decided to style in interface so it looked like Windows 95 to some extent. Having a kind of clunky ‘old-timey’ UI style made the game lighter hearted and also allowed me to go back to thinking about actually legible content for the interfaces. It pretty quickly settled into more of a desktop OS model of windows and dialogs popping up, with the user performing tasks that both looked and felt like work: typing, moving sliders, clicking on icons.

With the look settled, the content started being decided by the fact I was thinking about this project as part of the Speculative Play project I’m part of with my colleagues Rilla Khaled (who also happens to be my wife) and Chris Moore. That project is about creative interactive, playful media that speaks to alternate presents or near/distant futures. I positioned It is as if you were doing work in the context of the apparently near future of automated work (I read Rise of the Robots by Martin Ford recently in this vein). Thus the game poses as an application that humans who have been put out of work by robots and AI can play as a way to recapture the sense they once had of doing work and being productive. It’s a kind of semi-condescending service offered by this new world to those of us who can’t deal with it.

And that’s how the game came together.

(You can see the game’s process documentation for far more information about its development than you could possibly want.)

Google’s 49-qubit chip will allow them to develop a 49-qubit quantum system that can solve problems that are far beyond the capacity of ordinary computers: Google calls this goal quantum supremacy. The 20-qubit system that the Google quantum computing team is now working on currently boasts a “two-qubit fidelity” of 99.5 percent. The higher the rating, the fewer errors the system makes. Quantum supremacy demands not only a 49-qubit system, but also sufficient accuracy to achieve a two-qubit fidelity of at least 99.7 percent—which Google is on track to deliver by the end of 2017.

QUANTUM COMPUTING, QUANTUM SPEED

Google isn’t alone in their quest for advancing quantum computing. In 2016, IBM was running a 5 qubit computer, but by May 2017, it was offering beta access to its 16 qubit platform to the public for testing purposes. Furthermore, qubits alone aren’t the only consideration for actually achieving working quantum computers; error correction and scaling will also be critical to quantum systems. However, if Google does achieve quantum supremacy, it will be a major step forward.