By mswatcher
via sites.google.com
Published: Dec 24 2009 / 16:55
First think of the consumer of the API. Think about his likely situation and the problems he's facing. He doesn't want to learn a new abstraction and he doesn't like the fact that your API is going to make him change the design of his program. Design for the benefit of the consumer, not your ease of implementation.
-
Google Chrome becomes World’s Most Popular Browser
-
Chronoline.js - A Library For Making A Chronology Timeline Out Of Events On A Horizontal Timescale - Functionn
-
JRuby 1.7.0.preview1 Released
-
What You Need to Know About Linux Kernel 3.4 (released this week)
-
PhpDay 2012 conference in Verona
-
jQuery Scroll Depth - A jQuery Plugin To Track Page Scroll Depth - Functionn
Add your comment
