Vacation, disposable, and calm computing


Let me talk about vacation computing. The prime directive of vacation computing is that you should compute on vacation as little as possible. Neglect your email, abandon your social mediums. Don’t do the things you normally do, regardless of how computery your regular work is.

From there, it follows that your vacation computer should basically not be a computer. That means smartphones, tablets, and book readers are the only options. But smartphones are pretty much synonymous with social media, so they aren’t really viable as a vacation computer (though you probably want it anyway because they’re a superpower). Tablets are nearly computers now, so that’s not viable either.

It follows that a book reader is the only acceptable vacation computer.


Let me talk about disposable computing now. We put a lot of important stuff on our computers these days. Important passwords, legal documents, email, family pictures, private pictures, computer games, purchased and bespoke music, Hollywood and home video, etc. Sometimes those computers are in our pockets, sometimes they’re on our laps and coffee tables, and occasionally you might still find them on our desks!

For the drama and heartbreak that can occur when we lose these computers, we take astoundingly bad care of them. We don’t back them up, we reuse passwords. A moment without wireless networking is the worst and yet we don’t take steps to prevent even more dramatic losses due to password breaches and storage failure.

Given all of this, a computer is made better by making it a disposable object. Backup your data, and backup your backups. Practice good password habits as much as possible so your accounts are isolated and somewhat disposable. Know your gameplan and what happens to your stuff if your computer or backups fall into a lava pit.


Knowing about vacation and disposable computing, I’m led to an odd and dissonant conclusion: an e-ink Kindle is the perfect computer. It does not do work, it does not social media. You can take it through airport security without any extra steps, which feels a little perverse and seems a bit surreal. It does not interrupt, it does not beep or blorp, it just barely displays text. As modern computers go, it’s basically useless.

But. You can read on it. And reading is so wonderful. And you can put stress aside. A Kindle gets wet? Not a big deal. Drop a Kindle? Not a big deal. Try to use it by the pool, out in nature, out in weather, out where the internet does not go? Not a big deal. Lose your Kindle? Buy another one, it costs a fraction of all your other computers.

The one scenario where you will find yourself absolutely screwed with a Kindle is when you have to enter text. Logging into Amazon or a wireless network for the first time? That’s a bad time.

In every other respect, the Kindle is a computer that does nothing to increase your stress level. That’s pretty remarkable today. Let’s make more calm computing devices, ok?

Apple, Disney, and obsession

People in technology disproportionately like to comment on Apple’s products and business. Outside of technology, there are just as many folks who love to obsess over Disney’s theme parks. Based on my friend networks, I’d wager that for every person who obsesses over Apple’s keynotes, there’s a Disney enthusiast keeping up on special events and the best way to enjoy the theme parks.

The connection that strikes me is that both of these companies pay more attention to details than their competitors. Apple’s competitors throw software and hardware at the wall like spaghetti, hoping it will stick. Disney’s competitors rename their rides to match the blockbusters of summer. By comparison, Apple makes a big deal about the fit and finish of their hardware (let’s not talk about that camera though!) and has a coherent story about how all their products fit together into a useful landscape. Disney carefully arranges their parks to keep the guests in a cohesive movie world and pays attention to the little details that enhance or optimize the experience.

I could make some value judgement here about how attention to detail is more profitable, better design, better engineering, or whatever. I suspect all of those are true, but it’s not what excites me about Apple or Disney. When I read about changes to Disney’s theme parks or Apple’s keynotes, I’m excited that there are companies, quite large and successful ones, that are connecting lot of dots in an intriguing way. They’re extracting delight from large scale complexity. Megaprojects are nifty and often enhance humanity, but they’re mostly out of touch or sight. It’s nice that some of us can experience and enjoy these commercial projects of vast scale and quality execution.

Multiplication over management

When a developer becomes a manager, It’s not a promotion, it’s a career change:

If you want to do your leadership job effectively, you will be exercising a vastly different set of skills on a daily basis to what you are exercising as an engineer. Skills you likely haven’t developed and are unaware of.

Your job is not to be an engineer. Your job is not to be a manager. Your job is to be a multiplier.

Don’t miss the section on how we undervalue non-technical skills. It’s not unlike developing software, it’s just that your levers are people and processes instead of software and data centers. See also, Managing Humans.

Make systems from goals

Use systems to get where you’re going, not goals:

My problem with goals is that they are limiting. Granted, if you focus on one particular goal, your odds of achieving it are better than if you have no goal. But you also miss out on opportunities that might have been far better than your goal. Systems, however, simply move you from a game with low odds to a game with better odds. With a system you are less likely to miss one opportunity because you were too focused on another. With a system, you are always scanning for any opportunity.

Applies to personal life, biz, programming, hobby, whatever. Use goals to figure out what systems you need in place, then get habits and systems going to make those goals, or something better, happen.

Yet another way you can use your skills as a developer to construct a system that really solves the problem, and not a symptom of the problem!

Businesses can empathy too

Building an Ethical Business:

Empathy is sometimes described as a personal trait, but it’s a skill, a skill that can be learned, that can be honed, and that can be instilled as a core value of a company.

The post is about applying empathy to the core values of a business, how it shapes the actions and culture of the institution. But it’s a reminder empathy is about people, and how they experience you, your team, or your employer.

Follow up reminder: empathy is your most important skill. I’d go further than saying it’s a skill; those I’ve met with outstanding empathy basically have superpowers.

Stop me if you’ve heard this one

Lately, I find myself stopping to make sure I haven’t previously written the thing I’m currently writing. For starters, I have a horrible method for moving things out of my “I should finish this idea” folder into the “I wrote about this idea!” folder. It doesn’t help that I often draft articles in my head while I run, shower, or do chores and then forget that I had the thought. It’s kind of a mess in here.

Assuming that I slip up and write the idea down twice, hopefully it’s in a way that doesn’t look like I’m plagiarizing myself. Is it weird to write about the same thing multiple times, if it’s nearly the same idea?

I hate repeating myself, telling the same stories over and over. “Have I told you this one before?” is a frequent prologue to great stories. But is it necessary? Hearing a mediocre story twice is slightly painful, but hearing a great story twice is no chore at all.

If I keep writing an idea, coming back to it, maybe there’s something important there? Perhaps it’s still bouncing around in my brain for a reason. I haven’t fully wrapped my head around it, or articulated the idea in a way I find satisfying and essential.

This is a personal website; the line between “just play the hits” and “stop trying to make fetch happen” doesn’t have to be so strong here as it would on, say, the New York Times. So, stop me if I write about an idea so much I run it into the ground. It’s just that I’m trying to get it out of my head in the right way.

Bridge enroute to Chilas

Let the right something in

There will always be more somethings we want to do than we have time to do. Right? Maybe.

  1. A lot of the right somethings can add up to a great thing, even if the somethings aren’t of the highest quality or express the biggest idea.
  2. A lot of the wrong somethings aren’t that interesting, unless your work is generally of great enough import that historians take an interest in it.
  3. A lot of the wrong somethings may not add up to much at all and are unlikely to attract the interest of historians.
  4. If you don’t care about whether something’s great, you can produce a lot of somethings.
  5. If you don’t care if something expresses a big idea, you can produce a lot of somethings.

A lot of truisms will tell you that quality is the important thing and quantity is secondary. But perhaps there are all sorts of cases where that’s not entirely true.

Mozart wrote way more music than Beethoven; Beethoven’s was more sophisticated but their bodies of work are considered on the same level. There are way more episodes of Law and Order and all its spin-offs than Breaking Bad; one made more money, one gathered more acclaim.

Rather than deciding to pursue quality over quantity, perhaps it’s better to:

  • Choose your somethings with care
  • Execute on the idea central to those somethings
  • Produce as many somethings as possible without hating the quality of your work

The false bad guy

A pet peeve, in writing and thinking: introducing a false antagonist to create tension in a story. This is rampant in tech writing. Apple vs. Google, Ive vs. Forestall, Rails vs. Django, Ember vs. Angular, etc. But there’s no there, there. It’s only filling space.

I would love to have Ernest Hemingway weigh in on introducing a bad guy where one isn’t needed. I suspect there would be a lot of cursing involved.

Quit your desk

Things I’ve quit doing at my desk:

Many writers maintain a private writing hut. The hut has one purpose: it’s the place they go to write. They don’t do anything else there. Once they can’t write any more, they go do something else. I think we need to think of our desks in the same way: these are places where we get work done.

I like my desk, but I know the hours I can sit at it and get work done before fatigue sets in are finite. I try to mix in standing at our bar-height dining table, sitting on the couch (most recently, with three dogs), working from coffee shops and occasionally sitting on the front or back porch.

The big idea from that article, burning a hole in my head, is that we should step away from our desks when we’re not working (for me, telling computers to do things). Thinking can happen on a walk, standing outside, or in the shower. Socializing can happen from the couch or mobile device. Procrastinating by reading, surfing, social networking, etc. can happen anywhere.

Once I freed my mind from the idea that I’m only working the moments my butt is in a chair at a desk in front of a computer, my work improved and my life got better. Quit your desk and find out for yourself.

Coffee and other warmups

Making a cup of coffee sometimes helps me prepare for the process of solving puzzles with computers. Something about choosing AeroPress, French press, Chemex, or Clever; heating the water to 212F or 200F; medium-fine, medium, or coarse grinding of the beans. The weighing and grinding of the beans, boiling the water, rinsing the filter, pouring the water, waiting, pouring more water, agitating, pressing the coffee, discarding the filter and grinds. Now I’m left with a cup that I made for myself. A minor victory for the day.

All sorts of things require warm-ups. Stretching, air-squatting, or a quick jog lets my body know it’s almost time to exert itself. Word association or playing little games tells my brain it’s time to improvise.

Updating some documentation. A tiny, superficial refactoring or layout change to some code. Drawing a picture in my notebook. Making some coffee. That’s how I know it’s time to solve puzzles.