“I have so many things I want to do. But I’m constantly torn: should I polish the things I have in place, already? Or should I build new features that will be more attractive?” – me (basically), talking to my friend and coworker, Justin Gregory, at lunch.
It’s a constant struggle with me. I see the big, rusty patch in my software. I know it could / should be done better. But then, SQUIRREL! and off I go to build something else. Cause who doesn’t like new things, right?
“Why Do You Like Them So Much?”
I’m rattling off the various things that a service I use doesn’t have and Justin wants to know why I still use them.
It’s obvious to me. What they do have is so dang easy to use, I couldn’t imagine using any of the competitors. I tell him how easy it is to use the service; to get the results I need; to make the API calls. I don’t even have to think about the data structure. I just shove data in and the information I need comes back out.
It’s obvious. What they have is so dang polished, simple and enjoyable to use. Yes, I want those other things but I’m willing to wait for them, at this point.
So, What Should You Do?
Do you build something new, exciting and going to be awesome? Or do you polish what you have, making it the best it can be?
Justin asks me one more question as we’re about to head back to the office, from lunch:
When was the last time you talked about how much you loved a service that did everything, but did it poorly?