The manual labor of code

One day soon a robot will replace me. I'll be focused on some gnarly coding problem, happily munching on green grapes and slouching like the meatbag I am, when the interaction designer, call her Alice, will walk by and ask me if I want to go look at the neat new system she just installed. She'll say, "It's going to make our job much, much easier!"

The system will be matte grey and smooth like a river stone. We'll feed it a description of what we want and it will ask us some questions about what we're trying to accomplish. It will show us mock-ups and system diagrams and we'll give them the thumbs up or down. And then, after about three minutes of waiting and listening to the best hold music I've ever heard, out will pop a really good program. We'll tell the robot to give it a few more tweaks but really it will be fine to begin with. I'll try to look at the code but it won't be human readable.

The next week, the rest of the dev team and I will be let go. Alice will look bashful but relieved that she still has a job. I will move to the desert and start a business fabbing artful robot bodies.

Consider all of the startup people who have already been mostly replaced by robots: the IT team has been replaced by the cloud, the visual designer has been replaced by Twitter Bootstrap, the JS framework hacker by Dart, the DB guy by ORMs...

I can hear all of my literally minded peers screaming about the exceptions to that last paragraph. You're right, except that you're wrong. During the dot.com boom at i-drive we shipped a web site which could support a few million active users and we needed a team of 20 devs burning themselves out to make it happen. This year, two kids with fresh CS degrees and I shipped a site which can not only support a few million active users but also uses machine vision and crowdsourcing in a computationally intensive and complex manner.

All of that has happened in the time before engineers really put their minds to replacing themselves.

Like sectors on disks, checksums in packets, and registers on CPUs, we'll abstract away the manual labor of startup coding until most projects need only an interaction designer and the occasional consultation from a freelance computer scientist. It's what we do until we aren't needed to do it.

More posts

Recent posts

  • One Hour Fiction: The Panelist

    The pounding in my head is in sync with the ticking of the escalator steps as they rise from the netherworld of the convention center's floor. I pull a smile from memory and ignore the sweat in my eyebrows. So many happy attendees, clipping ...

  • Agreements: Fuel for the Engine of Business

    Note: This is an old post. I am now a CTO and no longer offer this service.

    The first person I watched run a company was Bly, the owner of a computer sales and service shop in Athens, Georgia. She gave me, a painfully young ...

  • What I hope Amazon is doing in secret

    Last weekend I had coffee at the wonderful Uptown Espresso with a friend from a nearby Amazon office. I write "a" nearby office because he's working on a multi-year project so secret that he can't even tell people which building he's in ...

  • Top 5 opportunities for growth in software

    I am a software engineering newbie. I thought that I knew a lot about it after I coded my first BASIC program on a TRS-100 way back in the before time, but now I see that the creation of software is a vast landscape of ...

  • It's safer in earthquakes, too

    "Trying to be happy by accumulating possessions is like trying to satisfy hunger by taping sandwiches all over your body." - George Carlin

    Happy Discardia, everybody! The weeks around the solstices are when we discardians let go of whatever is not adding value to our lives ...

  • Don't touch that dial

    I grew up in the future. My childhood room was next to an attic filled with science fiction so as soon as I could read I buried my nose in the universes of the great pulp era authors. I love it in that future because ...

  • The future-proof startup

    All of the production clusters I've retired have been ready to scale. As I pulled their plugs and listened to their disks spin down, as I slid them from their racks and thanked them for their service, each and every one of them was ...

  • What is "The Bear"?

    There was a distinct moment when I realized that I had completely borked the accounting system for my photo mapping startup. It was February of 2004 and I was living and working out of a tiny apartment in Berkeley and had spent two days tracking ...

  • Face down on the cutting board

    On the day I found out that my wife was cheating on me and had hired a divorce lawyer, I was defeated. I bailed out of the 3D web startup which I had been sweating over for years, leaving two of the nicest partners I ...

  • One big machine

    The infrastructure I use in teams and those I use for my personal projects are quickly diverging and it comes down to this question: What can one person do?

    When I'm working on solo projects like Transmutable Work or Science Saints the key word ...