ekivemark | Shared With: Everyone - Feb 15 2008 | news, Web2.0, Commentary, social graph, OpenSocial
ekivemark | Shared With: Everyone - Mar 15 2008 | web, it, news, web2.0, Commentary
ekivemark | Shared With: Everyone - Jan 14 2008 | google, news, social, Spock, People, commentary, Web2.0
This seems like Spock for the rich and famous.
Quoted: Geelong, Australia based Tinfinger has launched in beta today with a user-generated omnibus of famous and well known people. The site combines user-authored ...
ShareViewed: 1 Time
ekivemark | Shared With: Everyone - Dec 18 2007 | it, twitter, news, Web2.0, Commentary
ekivemark | Shared With: Everyone - Nov 27 2007 | it, news, Web2.0, Commentary
Dave Winer raises an interesting issue. If you develop an API interface - don't shoot for perfection! Once you have released your API in to the wild and it has been adopted by others then you need to preserve bugs and idiosyncrasies in the code.
Eliminating bugs in an API can introduce unexpected consequences that can break applications.
In a way I suppose this points to the fact that we should keep our APIs as simple as possible. The more feature rich, the greater the risk of issues.



Send Mark a friend request or a personal message instead.