It’s March 2009, the height of SXSW in Austin before the conference gets too big for itself. I’m hanging out downtown with tech folks from a blogging startup, having dinner and beers before we head to the party they’re putting on. The CTO, one of the first employees at the company, is talking about Memcache servers and MySQL scaling, and I’m hanging on every word. I love this stuff.
I’m a Mac and iOS developer, but I often take a break from native app development to work on server software. So I’m asking him about MySQL replication and what it’s like to run a schema migration without the database falling over. The conversation sometimes shifts back to Apple platforms, and he says he’s been thinking about going to WWDC. I had been attending WWDC for a while, so I say sure, it’s expensive but you should consider it. If you’re doing more web stuff, though, maybe it’s not as important that you attend.
We walk over to the party venue. It’s bigger and more crowded than he thought it would be. Their company has really taken off, growing well beyond the early days when it was just him and the founder trying to build something new. And it’s at this point that he turns to me and asks a question that brings us back to iOS development:
"So what do you think of my app, Instapaper?"
In answer to Marco Arment, at that time the CTO of Tumblr, I mutter something about liking it, but I haven’t really gotten it into my workflow yet. Hopefully whatever I said was encouraging. In subsequent years, of course, Instapaper would be one of my favorite apps.
Later, replaying these conversations, I realized that I asked the wrong questions and gave the wrong advice. About WWDC, I should have said “Yes, absolutely!” with an exclamation point. Buy a ticket. If you can’t afford it, go anyway because you need to be there.
But I didn’t say that because I wasn’t listening closely enough. I was so busy asking questions about Tumblr, that I wasn’t listening to the excitement in his voice about Instapaper. I was so busy thinking about server scaling and databases and all this other stuff that I could’ve learned from a book, that I didn’t hear what he was really saying.
I should have asked about iOS pricing, free versions, sales, UI design, who did the icon, what does the private API look like. But I didn’t ask those things because I missed the big picture, how dominant the App Store would become for distribution, and so I missed what mattered. I’d like to think that since then I’ve gotten better at listening.
Daniel Jalkut and I had Marco as a special guest on Core Intuition 200 not just because he’s a friend but also because he so well represents the goal that many of us have and our listeners have — to start our own company, to find success not just one time but again and again, and to have as thoughtful an approach as possible in the craft of software development.
This week I’m in Indianapolis for the Release Notes conference. While I will have some stickers for anyone interested in my new microblogging platform, and I’ll probably ramble about it at some length if asked, I’ll also be listening. I’ll be listening because you never know which random developer you just met will end up doing their best work in the years ahead, and you want to be as encouraging as possible, offer the right kind of feedback, and also learn from their perspective.
There’s a great line in the Pixar movie Ratatouille:
"Not everyone can become a great artist. But a great artist can come from anywhere."
I believe that’s equally true for developers. We often see someone go from nothing to a top app in the App Store. We often see someone start without an audience and then make friends on Twitter and blogs through the quality of their writing alone. And so we welcome new voices all the time if they’re respectful.
There’s been some debate about Overcast 2.0’s patronage model. Some of the discussion is healthy — how does a successful business model for one developer apply to other apps? — and some of the discussion is divisive. Instead of asking the right questions, it’s easy to jump straight to a conclusion with the dismissive statement: “that’s fine for Marco, but his approach would never work for other developers”.
The “that’s fine for Marco” attitude is poison for our community because it takes the opposite approach as that Ratatouille quote above. It implies that some developers have such an advantage that the rest of us shouldn’t even bother, because it’s not a level playing field. It’s true that some developers today have an advantage, whether through good timing or just a long history of shipping apps, but the lesson isn’t to give up; it’s to instead learn from it, and look at our own strengths. What small head start do we have that could grow into a great success tomorrow, too?
Rewind a handful of years, back to that day at SXSW when I could name plenty of developers who had more attention and success in our community than Marco Arment. You can be damn sure that didn’t discourage him from taking Instapaper from an “in my spare time” niche app to the top of the News section on the App Store.
I’ll never accept the implied negativity in the “that’s fine for Marco” argument. I’ll never accept that we should be jealous of another developer’s success instead of inspired by it to do our best work.
Conversation on Micro.blog