Rands In Repose: A Del.icio.us Interview
Popularity Report
 |
|||
|
|||
|
|||
|
|||
|
|||
|
Rank
URL Tag Cloud
Bookmark History
Saved by 23 people (-2 private), first by anonymouse user on 2006-03-08
- Ajeton on 2008-08-10 - Tags delicious
- Ejner8600 on 2008-08-06 - Tags Del.icio.us , interviews
- Isaacmao on 2008-02-28 - Tags :) , Del.icio.us , Google , SocialSoftware
- Exploreman on 2007-09-14 - Tags del.icio.us , imported , interview
- Evangineer on 2007-05-24 - Tags delicious , imported delicious , metadata , tagging
Public Sticky notes
The original headline for this article hit me last week in a post-Turkey haze.... laying on the couch... staring at the ceiling in the living room -- "Why Del.icio.us is more important than Google". Let's hear it for SENSATIONALISM! Woo-hoo!
Highlighted by feiyafei
The original headline for this article hit me last week in a post-Turkey haze.... laying on the couch... staring at the ceiling in the living room -- "Why Del.icio.us is more important than Google". Let's hear it for SENSATIONALISM! Woo-hoo!
Highlighted by feiyafei
The original headline for this article hit me last week in a post-Turkey haze.... laying on the couch... staring at the ceiling in the living room -- "Why Del.icio.us is more important than Google". Let's hear it for SENSATIONALISM! Woo-hoo!
Highlighted by feiyafei
A Del.icio.us Interview
Occasionally, gunfire is heard
The original headline for this article hit me last week in a post-Turkey haze.... laying on the couch... staring at the ceiling in the living room -- "Why Del.icio.us is more important than Google". Let's hear it for SENSATIONALISM! Woo-hoo!
It's hard to compare the two... one is a web service and the other is a company, but they do have a common goal -- they strive to manage the endless pile of information that is the Web. They are both viewed as doing a successful job of this as measured by their ability to provide their users with relevant information... quickly.
Highlighted by tzon02
A Del.icio.us Interview
Occasionally, gunfire is heard
The original headline for this article hit me last week in a post-Turkey haze.... laying on the couch... staring at the ceiling in the living room -- "Why Del.icio.us is more important than Google". Let's hear it for SENSATIONALISM! Woo-hoo!
It's hard to compare the two... one is a web service and the other is a company, but they do have a common goal -- they strive to manage the endless pile of information that is the Web. They are both viewed as doing a successful job of this as measured by their ability to provide their users with relevant information... quickly.
Highlighted by tzon02
A Del.icio.us Interview
Occasionally, gunfire is heard
The original headline for this article hit me last week in a post-Turkey haze.... laying on the couch... staring at the ceiling in the living room -- "Why Del.icio.us is more important than Google". Let's hear it for SENSATIONALISM! Woo-hoo!
It's hard to compare the two... one is a web service and the other is a company, but they do have a common goal -- they strive to manage the endless pile of information that is the Web. They are both viewed as doing a successful job of this as measured by their ability to provide their users with relevant information... quickly.
Highlighted by tzon02
From looking at del.icio.us from the outside, it appears you first design an architecture, throw it out in the wild, and then continue iteratively developing based off community feedback. Is this a correct observation? If so, how do you know when you've got enough of a product to throw it into the wild? Is it a conscious choice?
I develop in the live system directly. I get pretty much immediate feedback about what works and what doesn't, and I'm not above backing out a change I've made if it ends up working badly.
Usually I stay up really late hacking, and then as soon as I think I'm done implementing (but not debugging) I fall asleep. Then in the morning I fix all the damage
Highlighted by alaincrawford
How do you approach user interface design?
Lots and lots of iterations until something feels right. Avoiding features until the interface for them is apparent. Seeing how users use the existing features to do things I didn't expect, and then making those things easier.
Highlighted by alaincrawford
Public Comment