Follow that rule and you won't need to worry.
Follow that rule and you won't need to worry.
I think what you mean to say is "don't build a product that depends on LinkedIn", and to that, I absolutely agree. LinkedIn, with its chain email spamming and forced mass invites, is literally the post-child for internet dark patterns and unethical behavior. Furthermore, the sheer volume of people on there automatically force recruiting agencies to use bots (or at least copy-and-paste) to spam folks on there, and in general leads to bad returns for the recruiter and tons of spam for you the programmer.
Unless you have an ironclad contract with whomever you are partnering with(whose API you are using) and know exactly what you get from them and they get from you and for how long, you should not be depending on them.
If you want to spend a few weekends writing to some API and don’t care if the rug gets pulled out from under it, and all your users then fine. If you want to support an API in a product that will survive without that integration that is also fine. Just don’t gamble your entire product and your future user base on API's that can disappear overnight when some dickhead MBA decides he isn’t making his numbers and the free loader third parties aren’t worth it any more.
But to your point, LinkedIn's practices can be a little pushy, but the site still provides decent value to me (it got me my current job). I can put up with ignoring mass invite requests, recruiter messages, and configuring my notification settings to maintain this professional network. It may get me my next job in 5 years, so for me it's totally worth it.
Maddeningly, at least one dictionary disagrees: http://www.merriam-webster.com/dictionary/literally (2)
Name one product that doesn't rely on another product.
That said, I think that: "don't make your service depend on other services without some sort of contract or agreement to provide" is a better rule of thumb than the one above.
Basing your product on top of LinkedIn? The core of their business isn't anywhere near providing that API.
Building your company around the core business of LinkedIn/Facebook/etc is dumb, because you are nothing more than a complement to their core mission. Best case, you become a commodity and achieve modest success, but the oxygen gets cut off at any time.. If you're very successful, you become a feature of the mother product.
When you're Apple buying memory from Samsung, that's different. Samsung's output is memory chips... that's the business. If nobody buys memory chips, they lose money.
Developing for the open web and trying to get people to websites in the current mobile/social era is increasingly brutal unless you are willing to be completely dependent on a handful of big companies.