Buying Options
| Kindle Price: | $9.99 |
Your Memberships & Subscriptions
Download the free Kindle app and start reading Kindle books instantly on your smartphone, tablet, or computer - no Kindle device required. Learn more
Read instantly on your browser with Kindle Cloud Reader.
Using your mobile phone camera - scan the code below and download the Kindle app.
20 API Paradoxes Kindle Edition
| Jaroslav Tulach (Author) Find all the books, read about the author, and more. See search results for this author |
Every individual has a knowledge horizon. Objects close to us appear clearly, and as they recede toward the horizon, they become indistinct. What lies beyond the horizon is unknown, and yet we know there is something there. As our knowledge of the world increases, this horizon becomes more distant, and yet we continue to explore. It’s a phenomenon as ineffably human as Edmund Hillary’s “because it is there” reason for climbing Everest.
We test the limits of our horizon, we look around corners, and perhaps we find something bigger, faster, or more beautiful than we’ve ever known before. But sometimes, we find contradictions, as Darwin did when he explored the finches of the Galapagos Islands. His findings challenged orthodoxy, what he thought he knew.
Darwin’s observations were so paradoxical, that it was decades before he published his conclusions as “On the Origin of Species.” The whole process of scientific inquiry is based on our need to find answers to seemingly inexplicable questions, and as each old paradox falls to reason, we find new ones popping up at the edges of our horizon.
The world of software development and API design is no different in this respect. The more complex our systems, the more likely we are to bump into the limits of our knowledge. Our world is full of paradoxes waiting to be discovered and explained; it’s as natural as the process of evolution!
- LanguageEnglish
- Publication dateOctober 1, 2012
- File size1233 KB
Product details
- ASIN : B009NNXPES
- Publisher : WalrusInk (October 1, 2012)
- Publication date : October 1, 2012
- Language : English
- File size : 1233 KB
- Simultaneous device usage : Unlimited
- Text-to-Speech : Enabled
- Screen Reader : Supported
- Enhanced typesetting : Enabled
- X-Ray : Not Enabled
- Word Wise : Not Enabled
- Print length : 148 pages
- Lending : Enabled
- Best Sellers Rank: #2,296,701 in Kindle Store (See Top 100 in Kindle Store)
- #2,626 in Software Development (Kindle Store)
- #7,322 in Software Development (Books)
- #22,317 in Business Technology
- Customer Reviews:
About the author

My name is Jaroslav Tulach and I am the founder and initial architect of NetBeans, which is not just a well known IDE, but also the first modular desktop application framework written in Java. My name sounds Slavic and has a strange pronunciation (read the initial J as Y and last ch as in Scottish loch or in German Bach), because I am Czech. However, as NetBeans has been the flagship software product of Sun Microsystems/Oracle for a while now, you don't have to worry that content of my Practical API Design book might not be widely applicable and understandable.
Customer reviews
Customer Reviews, including Product Star Ratings help customers to learn more about the product and decide whether it is the right product for them.
To calculate the overall star rating and percentage breakdown by star, we don’t use a simple average. Instead, our system considers things like how recent a review is and if the reviewer bought the item on Amazon. It also analyzed reviews to verify trustworthiness.
Learn more how customers reviews work on AmazonTop reviews from the United States
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.