2,945 karma · joined September 26, 2009
hi@seanro.se
> Our mission is simple: connect the world's professionals to make them more productive and successful. When you join LinkedIn, you get access to people, jobs, news, updates, and insights that help you be great at what you do.
LinkedIn targets all professionals, not just those that are tech savvy. Most people visit only a handful of websites in a given day; if Linkedin can become a 'good enough' destination for professional news, it has a good chance of becoming part of that handful of websites, if it isn't already. There's some good insight on that here: https://www.quora.com/LinkedIn-Acquisition-of-Pulse-March-20...
Linkedin as a company isn't just about one thing, like adding professional connections for example, much like Apple as a company isn't just about one thing, like making iPhones. As a company, their goal is to build product(s) that align with their mission, and if the stock market is to be trusted as a proxy of how well they're doing that, it appears they're doing pretty well: http://finance.yahoo.com/q/bc?s=LNKD+Basic+Chart&t=1y
That's completely backwards. Dropbox started as a consumer tool and is now creeping into the workplace.
What you should derive from this, however, is not that you need to provide better support for that particular serialization format; rather, if you want to make this particular set of developers happier, you need to provide better support for that language they're using. In general, this means building SDKs for your API in whatever language your developers prefer.
When given the choice between building an integration with an XML API from scratch, building an integration with JSON API from scratch, and building an integration with an SDK that does most of the work for you, developers will generally pick the last option, regardless of how the data is being serialized underneath.
> But keep in mind, these aren't just problems that affect Dropbox... these are problems that many online storage providers have. Make sure to find out if your online storage provider can answer these questions before you trust them to secure your data in the cloud.
is particularly slimy.
And they're not even involved with this lawsuit.
I've always wondered how this was implemented:
> We keep a per-user version which reflects the state of the API the first time the user made an API request
The first and most likely point of failure is network issues (i.e. no Wifi or 3G access).
They have little to no revenue at this point and no current revenue streams that point to being able to generate anything worthy of a $2.5b valuation. I guess my point was that I'd like to know what revenue streams they are anticipating creating that would warrant such a high valuation.
A lot of companies completely miss the point of referrals. They say 'X% of our hires last year were referrals, so let's force everyone to blindly scrape their Linkedin networks and refer all of those people.' The highest quality referrals come when employees have actually worked with the people they're referring.