Computers aren’t fun anymore

Throughout The Dream Machine, a history of the early days of computing, tinkering and having fun was a recurring theme throughout the decades. I wasn’t around to experience the early days of computers myself, but they seemed to be genuinely exciting and rewarding . In the words of MIT sociologist Sherry Turkle: computers empowered their users, making them feel smart[er], “in control”, and “more fully participant in the future”.

Those feel like … odd descriptions for the modern computing experience. Using computers today doesn’t feel like an empowering experience. Sometimes it’s mindless and distracting. Sometimes, when a redesign rolls out, or your laptop doesn’t wake from sleep, it’s downright hostile. The experience of using a computer in 2020 is a concoction of data silos, dinging notifications, and reinvented wheels, presented in gratuitously bubble-wrapped UIs hyper-optimized by persnickety product managers and soulless A/B tests.

For most people, the computing experience is clicking around a lot, typing into disparate apps in which your data is trapped except through narrowly-defined, bespoke integrations, and struggling to find that thing you were just reading a few days ago among all the silos. This doesn’t make anyone feel smarter or more in control. It’s simply frustrating.

Software development is stuck in the doldrums too. A massive amount of cumulative engineering effort is spent rebuilding the same primitives1 because the software engineering industry hasn’t convincingly developed platforms at higher levels of abstraction2. A significant portion of development effort goes to placating not-invented-here-ness, where companies feel the need to build their own version of every feature, each slightly different (user familiarity be damned). A lot of software is little more than looking up API documentation and plugging one into another. There’s a dearth of creativity, of joy and discovery, of inventing something interesting and new. 

To be fair, computers — both the desktop kind and various mobile kinds — enable3 seemingly-impossible4 things5. But it feels frustrating to see the pioneering spirit that originally led to the development of modern computers giving way to uninspired flat interfaces6 and CRUD SaaS apps. The things you can do are limited to bespokely-implemented features, dribbled out only as fast as a small team of designers and developers can think of and build them. Of course you have an extensive list of things you wish your phone/computer/most-used apps could do; everyone does. You know the majority of it will remain a wishlist; there’s almost no hope of the feature you really want being implemented7. This isn’t empowering. What’s more, new features tend to be one-off improvements and ungainly new ways for you to do more work8, rather than adding or improving functionality in a generalized way so you can remix functionality and do things faster.

For the people who’ve figured out the right incantations to type and buttons-buried-in-submenus to click, computers can automate administrivia, surface information, and make them feel “more fully participant in the future”. But getting there is an arduous journey, and many people get in a place where computers just make things harder. The experience of using computers is, in various ways, awkward and frustrating (and maybe even dangerous9) for everyone. Computers were supposed to be bicycles for the mind. So far we only have penny-farthings.


  1. If you wanted to build a [web] app to do … anything, you probably have to start by setting up a database server, building a schema from scratch, possibly importing existing data or building a bespoke API-based integration, HTTP endpoints and request and response payloads. To build the UI you’re given little more than buttons and generic rectangles and an unkempt jungle of components and abstractions that may or may not be any good. Project setup scripts exist, but all that incidental complexity still exists in your codebase before you’ve even gotten to the intrinsic complexity of what you’re actually trying to build.
  2. I explored this on Twitter.
  3. Halide: RAW photography from the camera you already have that rivals the quality of much bulkier DSLRs.
  4. Concepts: An infinite canvas. Literally impossible without software.
  5. Spreadsheets: replaced roomfuls of human computers (literally, “people who computed”).
  6. Specifically, I’m referring to UIs that tend to have low contrast/readability, hidden functionality, and acres of space between elements that aren’t accessible via keyboard controls, only laboriously mousing. I’m not sure if flat design was the starting point for these problems, but I think it’s accurate to say it was an inflection point at least.
  7. Sometimes, someone builds a new app to address a feature gap. But building a new app requires a ton of effort just to get to parity with what already exists (see above), and this new offering will inevitably have feature gaps elsewhere.
  8. Justin Gage noted this on Twitter.
  9. From the benign case of accidental deletion to not being able to comprehend the deceptiveness of artifically-generated content.

Leave a Reply

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

WordPress.com Logo

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

Google photo

You are commenting using your Google 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 )

Connecting to %s

Create a website or blog at WordPress.com

Up ↑

%d bloggers like this: