The SaaS column over a , which I do enjoy, has a post on LinkedIn.. The author talks about how he gets LinkedIn requests from people who are out of work. I have never sent a LinkedIn request to get a job. If you are jobless it is too late to start using LinkedIn. Well not strictly true, but as Keith Ferrazzi says, “Build It Before You Need It.” I think LinkedIn is a powerful tool. I have asked people to introduce me to someone that I needed to know that they knew. Plaxo is useful to keep track of people. I have hundreds of contacts that are acquaintances that I want to be able to contact. Plaxo helps me do just that.
Monthly Archives: January 2007
I have been using Google as a development platform, specifically their custom search engine(CSE) functionality though Google Coop. I have been a developer for 7 years now mostly on the Microsoft stack of technologies but also on Linux, OpenGL, and various web stuff. I must say I am very disappointed in pieces of Google’s offering. Specifically the documentation. I admit that I have been spoiled by Microsoft which has excellent documentation. But Google’s was especially bad. I was unable to go beyond the rudimentary samples that they had without quite a bit of work. Their showcase which you think will be sample applications are not samples at all. If you want to do exactly what they make it easy to do than life is a snap, but if you want to really extend and build a cool web application than be prepared for some serious pain.
Venture beat, a VC blog, has a post on the riskyness of startups using Google as a platform. Google recently removed new access to their SOAP API which allowed developers to have an application which talked to the search engine. Canceling APIs will not breed any sort of loyalty and will make creating applications which use Google services more risky.
Dalai has a post about PACS customization that touches on something that I have been thinking about. The current state of what vendors call customization is sadly pathetic. Changing some options is not customization. The first and most basic method of customization is being able to build completely custom UIs. This goes far beyond hanging protocols and would allow the user to alter any visual element in the PACS. The second is having an open and documented API for third party software developers to build software that runs inside or on top of the PACS. This is a toolkit for programmers. The third would be a widget like interface, something like Google IG or netvibes. This would allow power users who are not software developers but are comfortable with editing HTML or other markup languages to make addins and UI widgets.
Why would a PACS vendor ever offer such a thing? Well why does Microsoft allow anyone to write software that runs ontop of Microsoft Office? The reason is simple. Software that is built as a platform is much more valuable than a standalone application. Open source office software is not going to have trouble trying to take market share from Microsoft Office because it is not as good, but rather because vendors and organizations have built thousands of pieces of software that add value to Microsoft Office, making it much more valuable than what comes out of the box.
The first PACS vendor to treat their PACS like a platform will have a real advantage. A good platform is hard to replicate. It is a strong competitive advantage. Do I see this happening? No. PACS companies are too busy replicating each others features to think about truly changing the industry. This is one time where a company should lead its users.
Guy Kawasaki has a post about using LinkedIn. I use LinkedIn and I love it. Social networking is not really a Web 2.0 thing. I have been a LinkedIn member for quite a while. In my opinion all serious people should have LinkedIn and Plaxo accounts.
Technorati Tags: LinkedIn