Rapid Application Development Building a site from scratch in 48 hours.

Don't you hate when you have an idea, and it's awesome, and you're totally going to act upon it, and then you don't actually follow through with it?

Wait. Am I the only one who does that? Anybody else? What about you over there on the other side of the screen? Okay, phew. That's what I thought.

Sorry for taking comfort in your misfortunes. That's kinda messed up. Anyway…

This happens to me all the time. I'm going to eat healthy. I'm going to read every morning before I open my computer. I'm going to walk 15 minutes every day.

I'm going to.

And usually I do for a few days. But then my excitement dies down. And life picks up. And there goes that.

(Temporarily) Unrelated Problem

I'm terrible at getting things done. I'm a perfectionist and that's not a good thing. Instead of doing I'm often thinking of the best way to do something. It's a crippling approach to life.

I'm working on a project now that is taking far longer than it should because I spend hours or even days on the tiniest details.


I need to figure out a way to be more decisive, be less of a perfectionist, and launch faster.

Can that be practiced? Let's find out. What if I forced myself to build something so fast that I had no choice but to turn my brain on silent?

Alright, here it is. I'm going to build something from scratch in 48 hours. It doesn't really matter what it is. Making and launching anything in 48 hours will be perfect practice. There just won't be enough time to be indecisive or to meddle over small details.

Sweet. I like this idea. I'm going to do it.

Crap. Back to problem #1. Am I actually going to do it? Or am I going to bail halfway? Am I going to be my usual self and take 48 days instead of 48 hours?

I really want to do this. I love the idea. But I know myself.

Hmm. I wonder if there is some kind of accountability tool that I could use to hold myself publicly accountable?

No, can't find any.


I'm going to use problem #2 to solve problem #1 which will, in the future, help solve problem #2.

Or in English: I'm going to use my 48-hour programming sprint to build an accountability tool.

Super Rapid Application Development For the Win

All of the above happened in or around my head on Thursday at 11:30am. I went with it. By noon I was out of the gates. And now, 48.5 hours later, I'm writing to you, my favorite reader in the whole world.

The deed is done. The site is built.

It was weird. And enlightening. I can't wait to do something like this again. It's too soon to say for sure, but I think this might have changed my life. Seriously.

How? Because my eyes were opened wider than I ever imagined they might be.

You see, I'm used to spending three weeks researching the perfect domain name. But for this project I spent less than 10 minutes. I went to instantdomainsearch.com and typed in the first thing that popped in my head. It was taken. I typed the second thing that popped in my head. It was available. I didn't have time to waste. I bought it. Done.

I'm used to spending days making a logo. But for this project, I just took an icon I was already using elsewhere on the site and called it my logo. Done.

etc. etc.

I'm used to doing things a certain way. And shortcuts are not a part of that way. But none of the drastic shortcuts that I took for this project harmed the end-result in any way. I like the domain name I chose. The "logo" is more than sufficient at the minimum viable product stage.

In fact, why am I even using the word "shortcut"? I didn't take shortcuts. I just trusted my first instinct and I didn't do four hours of due diligence for every decision.

This was something radically different for me. I loved it.