How To Design A Good API and Why it Matters (2007) [video]
1–10 of 22 posts
Re: How To Design A Good API and Why it Matters (2007) [video]
#2Someone should add (2007) to the title.
Re: How To Design A Good API and Why it Matters (2007) [video]
#3I think Android could have been much better if these principles were taken to heart during the design of the main APIs. From what I recall Josh collaborated with the Android team at some point; sadly too little too late.
IMHO almost every Android API i use violates some principle in this presentation.
Re: How To Design A Good API and Why it Matters (2007) [video]
#4I think Android could have been much better if these principles were taken to heart during the design of the main APIs. From what I recall Josh collaborated with the Android team at some point; sadly too little too late. IMHO almost every Android API i use violates some principle in this presentation.
So far I have spent more time on the NDK side than on the Java side, but for me the worst parts are the way Renderscript is bolted into the platform, all those m* member variables and anonymous classes everywhere.
Re: How To Design A Good API and Why it Matters (2007) [video]
#5This sounds just a lot my systems analysis and design classes years ago (waterfall days). Who would think of gathering requirements and specs in these days of Agile....
Re: How To Design A Good API and Why it Matters (2007) [video]
#6This sounds just a lot my systems analysis and design classes years ago (waterfall days). Who would think of gathering requirements and specs in these days of Agile....
And Facebook showed clearly that you can change your API daily and no one cares.
Re: How To Design A Good API and Why it Matters (2007) [video]
#7This sounds just a lot my systems analysis and design classes years ago (waterfall days). Who would think of gathering requirements and specs in these days of Agile....
And Facebook showed clearly that you can change your API daily and no one cares.
Well, a lot of people care it's just that they don't have another option.
Re: How To Design A Good API and Why it Matters (2007) [video]
#8Someone should add (2007) to the title.
Someone at your service. Kind of interesting that this was posted 15 times and never really discussed:
https://hn.algolia.com/?query=How%20To%20Design%20A%20Good%2...
Re: How To Design A Good API and Why it Matters (2007) [video]
#9And people say there's nothing copyrightable in an API design...
Re: How To Design A Good API and Why it Matters (2007) [video]
#10And people say there's nothing copyrightable in an API design...
Just because something is a creative act doesn't mean it's covered by copyright. If your functional creation is useful and novel, get a patent on it.