• Skip to primary navigation
  • Skip to content
  • Skip to primary sidebar

Simplicity Rules

Adam DuVander on keeping it simple

  • About Adam

Good Enough Does Not Mean Finished

December 20, 2017 by Adam DuVander

It’s the most famous portrait of the first president of the United States. You’d have never seen it if the artist waited for it to be finished.

Gilbert Stuart’s 1796 painting of George Washington went on to be used for the $1 bill. So, if you’ve ever held a buck, you’ve seen his work.

Stuart also painted portraits for five other presidents, two first ladies, a chief justice of the Supreme Court, and Napolean’s brother. Yet, this George Washington portrait is his most famous work. But we rarely see the full canvas.

That’s because Gilbert Stuart decided it was “good enough” as-is. Good enough for him to copy more than 100 times on other canvases. Good enough, eventually, to be on multiple postage stamps. Good enough for US currency!

Even though this was 221 years ago, Gilbert Stuart was doing what The Paradox of Choice calls satisficing. Once the portrait met Stuart’s criteria, he was done. In this case, it had to be good enough to use as a template for other paintings.

The key there is determining the criteria and being willing to settle for far less than perfection. The original iPhone wasn’t that great, but they released it anyway. They had a chance to make incremental–and over time, major–improvements.

You can do the same with whatever you’re working on. Whether it’s a side project (remember the side project lifecycle), an initiative at work, or you’re cleaning the house.

Be willing to keep some canvas empty. It doesn’t have to be permanent.

All I Really Need to Know I Can Learn on Wikipedia

December 14, 2017 by Adam DuVander

Recently I picked up a book I first read in fifth grade. It was a book I really didn’t have any business reading when I was ten years old, but I remember liking Robert Fulghum’s humor in All I Really Need to Know I Learned in Kindergarten and its sequels. It also probably helps that each story is short (less than five pages in my small paperback version). I may appreciate that even more as an adult.

The book was first published in 1986, and its stories reference much earlier times, all well before technology and the Internet became ubiquitous. I’m not sure which are the simpler times. In the book’s first story, I found myself reminiscing about how information used to be gathered:

Spiders. Amazing creatures. Been around maybe 350 million years, so they
can cope with about anything.

At some point in the writing process, someone had to source that arachni-fact. Maybe it was within the “S” volume of their encyclopedia set, or a thick book of trivia. Otherwise, it would require a trip to the library and a search for the right reference book.

As I quickly type this post into my cloud-hosted blog software, I opened a new tab and got a similar answer in seconds. I didn’t even write out my complete question, because Google suggested this search based on many other curious humans.

We already know that many things have changed because of the Internet. Reading Fulghum’s “uncommon thoughts on common things” from over 30 years ago sent me thinking about the other efforts required for him to publish his book:

  • He may have written longhand on yellow legal pads, or typed on a manual typewriter. Once he saw success, perhaps he bought an early and expensive “personal computer.”
  • Drafts were likely typed and mailed to the publisher. By the early 90s, maybe he faxed edits.
  • He was discovered when a printed copy of his story was sent home with school children, one of whom had a literary agent parent.

Today, he’d likely write directly into a relatively inexpensive laptop, perhaps using writing software within a web browser. Feedback and edits could all happen within the same document, which could then be exported for publication.

Or maybe he’d just have a blog, which, of course, he does.

Run Through First Base

December 4, 2017 by Adam DuVander

In baseball, first base is different from second and third. You can touch first, run past it, and still be safe. This rule means that once you hit the ball, your only objective is to run as fast as you can all the way through first base.

Everybody stretch: run through first base
Paul L Dineen

If your hit went right to an infielder, it’s tempting to give up and jog. Even if you’re certain you’re safe, it’s natural to slow down as you approach your destination. But that means running to, not running through.

▓▓▓▓▓▓▓▓▓▓▓▓▓▓░ 92%

— Year Progress (@year_progress) December 2, 2017

It seems like the year is almost over, but as my friend Heitor tweeted, there is 8% of the year left. If 2017 is the 90 feet between home and first, there are more than seven feet remaining.

I’m going to run through December 31.

Rhymes With Happier

October 24, 2016 by Adam DuVander

Recently I was telling a friend about a new career opportunity. As I explained the company and the role, he started laughing. That wasn’t really the reaction I was after, so I stopped talking.

“What?” I asked?

“It’s just that this sounds like exactly the perfect place for you,” he said.

I’ve been a Zapier fanboy for some time. Now I’m stoked to be the first at the company devoted to “developer marketing” (in quotes because developer marketing doesn’t exist). While Zapier customers are primarily non-developers, partner companies connect their APIs to Zapier. I’m helping those technical people make better integrations so everyone can be happier.

Ooo! Zapier rhymes with happier. It’s like they planned it that way.

Bryan Helmig, Mike Knoop, Wade Foster (Zapier founders)

Three and a half years ago, I met Wade (far right) at the Small Business Web Summit. I had organized the API track, and Wade came to talk about Webhooks, sometimes called a “reverse API.” While it’s a bit techy, the things that they make possible are very cool. Services that incorporate Webhooks can alert other services as soon as something changes.

Zapier allows you to connect 700+ applications (Google Sheets, Trello, Slack, etc.) together and automate your workflow. Do you want a text message when you receive certain survey responses? That’s the sort of stuff Zapier does. “We’re just some humans who think computers should do more work,” reads the Zapier about page, which now includes my smiling mug.

In early 2014, I gave a workshop at SXSW about “Un-Programming.” Zapier figured heavily in the curriculum and I’ve continued to use it for my own ever-expanding list of automations.

I also kept in touch with Wade, who eventually introduced me to others on the team. The people (100% remote all over the world) are great, I was already a fan of the product, and the company had a position that made a ton of sense given my background.

I’m really, super excited about the work ahead.

Want to follow along? The best way is to subscribe to the Zapier engineering blog.

The Side Project Lifecycle

May 7, 2016 by Adam DuVander

I love side projects. It’s fun to dive into an idea, make it happen, then share it with the world. I also love the term side project because it sets reachable expectations. It also means there is room for more than one. Yet, there is not unlimited room. At some point a side project needs to move on, away from its creators care.

Side Project Lifecycle

The majority of a side project’s life is spent in either maintenance or decline. All the fun of a project is in the early half of the lifecycle. That’s where the creative energy is bursting, propelling through to MVP (remember when to buy the domain name). Sometimes that activity carries on through the improvements part of the cycle. Rarely, you can extend that section, if you really have a lot of interest.

Most commonly, side projects enter maintenance or decline. No matter which it is, they don’t have the same vigor as the earlier stages. Maintenance and decline take time or energy (usually both) from the new projects you want to build.

Compare APIs with my Newest Side Project

Ever since I left ProgrammableWeb, I’ve wanted to dive deep into just the subset of public APIs that every developer needs to know. These are the APIs that fulfill a purpose beyond supporting an application or service. The API is the service.

EveryDeveloper comparisons

EveryDeveloper launched in early March, gaining a lot of interest. I’ve been keeping the fire stoked (improvements stage) since, exploring related topics on its blog and on Medium.

Making Room for More Side Projects

I have written about several side projects on this blog over the years. One that got a lot of attention was a site to help find WiFi in coffee shops and other public spaces. WifiPDX launched in 2004, when there were only 54 spots in Portland to find WiFi. Now, of course, it’s practically ubiquitous.

Though I relaunched in 2012 that was basically the last time I made any improvements to the site.

WifiPDX designs: 2004-2012
WifiPDX: Portland's wireless internet connection, 2004-2016

I did little maintenance over the last four years, but not for lack of need. Spam listings and reviews littered every page. The design wasn’t responsive, which made it very difficult to use on mobile devices (which is now likely the primary use case). Most importantly, I’m no longer interested in taking it on as a project.

To make room for EveryDeveloper, and whatever else I may do next, wifipdx.com now has a simple epitaph on the home page. And all pages redirect to it.

This side project has completed the entire lifecycle. The prospect of making this decision was sad, but making it was exhilarating. I felt the energy release, no longer held by WifiPDX’s needs.

After 12 years, it’s time to make room for something else.

What do you need to let go?

  • « Previous Page
  • Page 1
  • Page 2
  • Page 3
  • Page 4
  • Page 5
  • …
  • Page 85
  • Next Page »

Simplicity Series

  • Designing the Obvious
  • Paradox of Choice
  • Laws of Simplicity

Copyright © 2025 · Elevate on Genesis Framework · WordPress · Log in