- File Size: 1233 KB
- Print Length: 148 pages
- Simultaneous Device Usage: Unlimited
- Publisher: WalrusInk (October 1, 2012)
- Publication Date: October 1, 2012
- Sold by: Amazon Digital Services LLC
- Language: English
- ASIN: B009NNXPES
- Text-to-Speech: Enabled
- Word Wise: Not Enabled
- Lending: Enabled
Amazon Best Sellers Rank:
#1,130,387 Paid in Kindle Store (See Top 100 Paid in Kindle Store)
- #1337 in Kindle Store > Kindle eBooks > Computers & Technology > Programming > Software Design, Testing & Engineering > Software Development
- #4531 in Books > Computers & Technology > Programming > Software Design, Testing & Engineering > Software Development
- #435022 in Kindle Store > Kindle eBooks > Nonfiction
20 API Paradoxes Kindle Edition
"Enlightenment Now: The Case for Reason, Science, Humanism, and Progress"
Is the world really falling apart? Is the ideal of progress obsolete? Cognitive scientist and public intellectual Steven Pinker urges us to step back from the gory headlines and prophecies of doom, and instead, follow the data: In seventy-five jaw-dropping graphs, Pinker shows that life, health, prosperity, safety, peace, knowledge, and happiness are on the rise. Learn more
Enter your mobile number or email address below and we'll send you a link to download the free Kindle App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.
To get the free app, enter your mobile phone number.
Customers who bought this item also bought
Would you like to tell us about a lower price?
Top customer reviews
There was a problem filtering reviews right now. Please try again later.
This book is different though and I am glad that I bought it. It's much shorter (I read it during my subway rides to the work in two weeks or so) and chapters are great mixture of comprehensiveness and brevity. Each chapter introduces an interesting paradox of API design and it's described in the way you probably haven't thought of yet. Some of these paradoxes where much more interesting for me (Coolness vs. Cost, Backward Compatibility, Callers and Providers, DSLs ...) than other ones, but I am sure that every developer will appreciate something else. But since it has 20 distinct chapters, you can just skip ones you're not quite interested in.
So compared to the previous one, I feel like this is an improvement. If you happen to be API designer, then it's no-brainer. If you happen to develop standard enterprise software then you probably have greater flexibility to redesign your APIs and you don't have to think so much about things like backwards compatibility etc. But I'd still say that information provided in this book would be useful to you.
I am giving it 4 out of 5 stars, because some of the weirdness from the original API Design book also leaked into this one, but note that this is very subjective opinion.