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 is "nimble". Each new technology has to earn its place by reducing demand on my most precious resource, time.

Science Saints has no database, no web app, and no compiled code. It's a set of static HTML and JS file that reads a hand edited JSON file holding the saints data. It's served from an AWS instance running nginx that I'm using for other projects but it could as easily be served from an S3 bucket. I don't manage it, I just make it.

Compare that to what I build with teams like the one I work in at Captricity. In order to support our customers' need to turn information on paper into information in a computer I've built a snazzy editor for uploading images, defining what fields they want converted, and then seeing the results. If we cut some corners, one person might be able to manage that. But then there's all of the machine learning and mechanical turk code, the ops tools, and soon we're looking at a dozen people working long hours.

The goals of those projects are radically different but the fundamental actions of the people aren't: Think a thought then make it so.

It's the acceptance of complexity which makes multi-person projects different.

My capabilities in one person projects are growing faster than my capabilities in multi-person teams. Tiny, comprehensible web engines like go-json-rest are combining with the complexity reduction of single-page apps and style foundations like Bootstrap to start one person projects far ahead of multi-person projects which feel the need to differentiate their tools and style.

On solo projects I don't even consider buying hardware, laying my own network, or investing in storage. I push from GitHub to Heroku via and deal with the occasional hiccup. Or I spin up a single, increasingly powerful AWS instance (One Big Machine) and rely on RAID and offsite backups to recover from occasional disasters.

More than just bringing new techniques into larger projects, I feel like we're heading towards a time when there are two, somewhat separate ecosystems: one for solo projects and one for large groups.

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 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 ...

  • 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 ...