I've always been a "kitchen sink" programmer because that's the way I was taught to do it, and it's part of the fun of the job: anticipating everything which might go wrong and pre-empting it. Unfortunately, I noticed that I am a mere mortal anyway, so I could never anticipate everything.

Then about the same time I noticed that people would fall in love with very sucky products if those products did the core "thing" correctly. Crappy interfaces, poor layout, confusing buttons - didn't matter as long as people could work out how to do their task and get on to something else.

So, the next question I had to answer: why not just build something you consider sub-par in the hope that it will be useful to others, and perfect it later? Thinking like that lets me focus on what matters rather than wasting time working out which AJAX library to use or which colours would look best. Perfectionism really isn't a trait I admire any more.

Well, I have a reputation to protect as an interaction designer. I'm kinda a microcelebrity. People who know me have a high expectation of my work. (Surely not as high as I think, though, I'll give you that.)

But for programmers with little user experience experience (urk), your point is a good one.

One example of what I'm thinking of is the tarsnap website. Nothing fancy, and Colin mentioned in a blog post he'd rather get the code for his product right first (and from what I've seen it's good stuff) then work on the website. So sure, if you're an interaction designer you have to do the Right Thing. But it's easy to get paralyzed in the face of what looks like an overwhelming task when you should just pitch in, accept you're going to f*ck up to some extent, then rework it.

I failed a project last year through being too perfectionistic, so I'm trying to retrain myself not to be. Frankly, my standards were much higher than the clients' and I could have done half the work and been much more successful.

> accept you're going to f*ck up to some extent, then rework it.

Oh, I'm totally with you.

My app is far from finished. The settings area still sux. And we use lightbox-style overlays in a few places and I hate those suckers. And there's a lot more that I want to do with it, like, NOW.

But we did ship on the day we said we would. :)

The main reason we were able to do that was to first identify which missing "killer features" would not be apparent to people other than us. We, of course, had the perfect 2-years-down-the-road mental image of our project. We could never ship that.

But other people, coming to the app as newbs, would not know that we managed not to include <killer feature here>.

Then we ruthlessly qualified things as "good enough." I can't tell you how many times I said "Eh, fuck. Just ship it. We can make it better later."

I just wouldn't compromise on data entry. That's the whole point of the app. Then again, we didn't compromise on what we had, BUT we did leave out the other entry mode (still working on the design, a month later). So...

So this is the letsfreckle.com site? Looks really good, must be fun :) If I was still freelancing it looks like something I'd actually use, unlike 90% of webapps out there.

Yeah, just discovered this myself. Looks like a super-professionally built and designed web app.

That's a nicely designed site. Kind of a relief from the standard "Rate my Startup" submissions we've been seeing here lately. Makes me want to hand you money and try it out, even though I don't actually need the product!

On topic though, I'm also a big fan of releasing the "Meat" first and filling in the rest later. S3stat went live with a completely blank "Features" page and no way to charge CC's. Like you say, a 30 day Free Trial means that you don't have to actually be capable of processing payments the day you launch. It's a good motivator to ship that code though!