Pathologically Entrepreneurial
Big release for RescueTime today. I have no time to write about it (and probably oughta write on the RescueTime blog if I did have time… which I promise I’ll do).
If you’re a RescueTime user, check it out and let us know your thoughts!
Everyone with a fine liberal arts education should be familiar with Zeno’s Dichotomy Paradox (props to Steve Leroux for helping me remember his damn name).
“Suppose Homer wants to catch a stationary bus. Before he can get there, he must get halfway there. Before he can get halfway there, he must get a quarter of the way there. Before traveling a quarter, he must travel one-eighth; before an eighth, one-sixteenth; and so on.”
I can think of no better description of software development releases (or product development in general). At some point you have to say “fuck it”, fall forward, and confound Zeno. Throw caution to the wind and ship too early and you ship crap– and your users know it. Aim for perfection and days stretch to weeks as each day brings you asymptotically closer to greatness (which sucks the life out of any team, IMO). I know teams who literally have worked for a year or more without shipping anything to anyone. I don’t know how they can do it.
But, any way you slice it, those last few days before a release feel like you’re wading through rancid molasses.
There has been a lot of chatter lately about alternatives to Silicon Valley. There is no denying that Silicon Valley produces more startup success than any other town. But is it cause or effect? Does SV add some secret sauce to the startup recipe or is it simply a place where a lot of geeks tend to congregate?
For starters, it’s a good idea to read Glenn Kelman’s outstanding post on Seattle as a startup hub, inspired by the New York Times piece on the same topic. TechCrunch fairly quickly blew the post out of the water, causing Glenn to post a solid (and humble) response. And, causing Alan to point out that Arrington is “being a wanker”. Fun stuff! I I’m a big Arrington fan, but I’ll second the sentiment… It’s easy to crap on an upstart. Windows people have been doing it to Mac people for years. “You’re so far behind, why are you even trying? It’s almost pathetic,” they say. Strange that you don’t hear that too much anymore from the Windows camp. Never count out an upstart!
As a founder who is currently hip deep in the YCombinator experience in Silicon Valley, my initial inclination was to return to Seattle in March. I’m currently rethinking that sentiment (but haven’t made any sweeping decisions). The purpose of this post is to publicly run through some thoughts on this and get some feedback.
As mentioned by just about entire world, Silicon Valley births more startups than anyone. By a huge margin. It’s ridiculous how far it is ahead of upstarts like Boston, Seattle, Austin, etc. It’s obvious to me that there are many more startup PEOPLE in SV (which is a big reason for the number), but are there factors there that make startups more successful? I’m going to run through the thing I think are critical for a startup and how I think SV adds to them. Call me out if I’m wrong or if I’m missing anything:
It’s probably safe to say that each of the above points carry different weights for different startups. A company like mine might not care much about great startup lawyers, but a company like Avvo might. A company like Twitter clearly cares an awful lot about funding– it’s a big play with a ton of upfront expenses and no immediate way to make a pile of money. But for a company like mine (which, ultimately, is probably going to live or die based on the value we can provide to businesses), will living in Silicon Valley give us enough of an edge to justify the expense and distraction of moving?
RescueTime will never be a purveyor of widgets (as a primary business), but there’s no denying that widgets are a damn good way to spread the word about your product, assuming that anyone actually wants to install them.
A widget that displays exactly how you spend your computer time may be creepy to some. As an old skool fella who is a bit more privacy-focused, I never really thought that a widget belonged anywhere on our near-term product roadmap. However, when we did our “What features do you want?” survey, thousands of people filled it out… 26% of ‘em expressed interest in a widget.
Sooooo, we built widgets. You can see mine to the right hand side of this blog– it’s a real time report of exactly what categories of my computer time I’m spending the most time on.
As we started thinking about it, RescueTime widgets could be used for all sorts of fun stuff:
Widgets are officially a beta product– we’ve got a few kinks to work out. For example, in Firefox there is a Flash bug that results in the status bar continuing to report “transferring data from RescueTime.com…” even though it’s not (you can switch to a different tab and back to make the message go away). Anyone know how to fix this?
I love the idea of contextual advertising, and I think Adsense has been a boon to entrepreneurship across the world. But it’s clearly broken. Today we received some nice feedback about RescueTime:
from A RescueTime User
to team@rescuetime.com,
date Feb 9, 2008 1:27 PM
subject RESCUETIME APP FEEDBACKgreat site!
put some adsense here and i’ll click it every time i come here!
This is the 3rd such email we’ve received, and given that the concept of PPC advertising is increasingly well understood, is not an uncommon sentiment. Internet software has to be free, right? If so, how can a thankful user reward a company?
I wonder how advertisers feel about this? It’s no wonder that Adsense earnings are sharply dropping.
I just posted what I thought was a pretty darn interesting post about Google’s dominance in my life. By my count (and, with RescueTime, my count is pretty damn accurate), 13% of the time I spend in front of my computer is taken up by Google products.
Note that this is COMPUTER time– not just my online time.
This Tuesday, I’m going to get a chance to meet Kevin Hale, who is the designer behind Wufoo and proprietor of ParticleTree. Kevin wrote a blog post last month that I think is one of the better summations of what it means to be a web designer. While I don’t want to dwell on the negative, Kevin has a pretty good description of why I hate to refer to myself as a designer (whether it’s “web designer”, “ui designer”, “interaction designer”, or whatever).
“For most designers, the relationships they care about most is the one they have with the design. They seem to only love the design and more often than not, they tend to love the design too much. These designers focus on their legacy at the expense of the audience. The user can suck it. You can hear it in the way they talk about the design and how they talk about their users. They’re arrogant and defensive.”
“…When I started working on Wufoo, I was definitely a bad designer. I thought I was hot shit and knew all the answers. I saw the user as a wild beast that needed to be tamed. He got in MY way. Use the tool the way I designed it, fool—not the way you think it should work. Thinking back, I remember being angry all of the time.“
Another great bit:
“On a web application, the design breathes and exhales through customer support. I’m so glad we have Chris on our team. He’s our customer evangelist. Through him, I’ve come to believe that there’s nothing more important than to monitor and man those incoming emails and respond as quickly as possible to every single inquiry, request and comment. It’s the pulse of not only the application, but the business as well. It’s in support requests that Wufoo lets us know when something isn’t working. It’s there that she lets me know when I’ve done something right.”
Give it a read.
Launching a big batch of new stuff is ALWAYS hard. It’s a lot of work and you’re generally making a substantial bet on some of your own instincts.
Since the launch (a few hours ago), feedback has been pouring in. Much of it is positive, but some is negative– which I think is par for the course any time you change a utility someone is used to. If you’re a RescueTime user, please log in and give us your honest/brilliant feedback!
A reader took the time to shoot me an email with a few questions about design and startups… His questions were interesting enough that I thought they might be worth blogging about. So here goes:
Question #1 - What is the priority balance between programming and design/UI?
In my opinion, it totally depends on your startup, and where the core of your innovation lies. Take a hard look at the problem that you’re attempting to solve and why the current solutions to that problem are inadequate. As Paul Graham says, there’s no shortage of things that suck… presumably, you’re setting about to make something suck less.
How? Are you going to make it faster? More fun? More reliable? Cheaper? Sexier? More powerful? More viral? More social? When you’ve got a match between how you propose to innovate and the skills that your founding team has, you’ve got an exciting opportunity.
I should point out that brilliance can (and often does) manifest outside of a person’s core skillset… I think a person with a background in marketing would never conceive of the viral marketing machine that is Feedjit (the person who did is a PERL coder with a background in systems engineering). I don’t think a person with a journalism background would think that Digg or Reddit were such hot ideas. Innovation can (and often does) come from people who aren’t familiar with the “common wisdom” that maybe shouldn’t be so damn common.
But assuming a big part of your innovation revolves around “creating a better user experience for X”, you need someone who can create great UI. And while people who don’t dream in pixels and CSS can have flashes of UI brilliance, there’s no substitute for a great UI guy on your team.
I’m not going to go into detail, but obviously there are about a billion scenarios where coding is AT LEAST as critical as design. I’ll leave that blog post to someone else.
2. Should we have a layout/ UI figured out before programming has begun? (this is actually in retrospect, because we’ve already begun programming)
I’m a big fan of agile/scrum style development and the iterative design that goes along with it. That being said, I think the idea of having a cohesive vision in the form of a visual prototype is a great guide to build off of (just don’t be married to it). Making design shoot-from-the-hip-agile from start to finish can oftentimes result in a bit less focus and a product that looks duct-taped together.
3. If we are planning to have Facebook app/ MySpace widget a la Slide or YouTube, would it be best to focus on destination site, or on the widget side first?
Joe Kraus recently spoke at a YCombinator dinner and espoused the virtues of chasing the trends. I’ve always referred to it as the idea of “finding a parade and then marching in front of it”. I’d want to know more about what you were building, but on the surface I think that jumping on the Facebook bandwagon is worth doing if you think Facebook users will sign up. A lot of things won’t play well on Facebook (you won’t see us building a RescueTime Facebook app any time real soon). That being said, I’m not real bullish on Facebook’s long term future (from a platform perspective). A lot of the top Facebook apps are down as much as 70% from their peak usage.
I don’t imagine too many people who read this blog would be terribly interested in this, but I have to crow about it anyway. Joe (cofounder and roomie) and I figured that the move to Silicon Valley was an ideal time to adjust our diet and shave off a few pounds.
Since arriving (Jan 4), I’ve lost just over 9 pounds or (as I like to think of it) 36 sticks of butter. This is all with only nominal excercise and eating just about as much as I want. Joe (always the showoff) has lost 15 pounds.

If anyone cares, this was done with a “lazy” South Beach diet. Lots of veggies, plenty of lean meat/fish, and functionally zero sugar/simple carbs.