making linkedin a platform

recently, i have been spending some time on linkedin. of all the social networks out there, it has the most appeal to me: there is less nonsense on it, and people are motivated to use it for work. bergie had this link to an essay on linkedin as a platform play that i wanted to comment on.

full public profile

There’s still a tragically high barrier to entry: without logging in to LinkedIn, you can only view a summary of the profile. This is total crap: it doesn’t make it easy for me as a user to extend the reach of LinkedIn. I’d love send that URL as my resume to people, but if they have to create an account to log in to LinkedIn, I’m not going to do it.

my public linkedin profile is already in the top 20 google results for my name. making this more full-fledged would allow people to better take charge of their public image on the internets (something increasingly important)

show linkedin data elsewhere

For example, it’d be awesome if there was a JavaScript include that would list people’s endorsements of you. I’m sure people would love to put that in their blogs. And it’d be great for the coders out there if all the data in LinkedIn could be retrieved with simple REST calls that returned simple, XML formated data-documents.

linkedin has a lot of (currently dormant) currency it could use to become an important platform for user ratings. just like ebay has its seller / buyer ratings, the endorsements are quite valuable, but are locked into linkedin today. the system would need better ways to deal with people who game the system, but it is off to
a terrific start.

linkedin RSS feeds

It’s frankly shocking that there aren’t LinkedIn feeds for events that occur in your social network. When someone gets a new job, you get an endorsement, someone else gets an endorsement, someone adds a new contact…all those activities that people may want to respond to are locked up in the system.

we are all busy, and who remembers to always go check the linkedin homepage for new things happening? that’s so 1998.

company ratings

You could even imagine something like this: people can write in their experiences applying for jobs at different companies. When you ask LinkedIn to send you resume to a job, it could tell you people’s over-all feel for that company. That’s the kind of collective/emergant wisdom that only a hosted application like LinkedIn can do.

companies are people too :) (according to the law). why not make it possible to see how a company is viewed overall?

company drill-downs

Speaking of hosted applications, LinkedIn could become the org-chart application for companies everywhere. Most large companies I’ve worked at had that funky applet you could go to in the intranet and pan through the org-chart. LinkedIn already has a ton of data that people have agreed to put in the clear. Instead of those boring, information skinny org-charts you’re used, LinkedIn could provide a much richer, and fatter org chart. Want to see endorsements that people have given Jane in IT? Does the fact that Jack has no endorsements mean you should avoid giving him The Big Project?

i am sure a lot of people are already using linkedin to reverse engineer org charts from companies they do business with. why not make this easier? if you are concerned about headhunters, offer a more
competitive / attractive work environment.
is linkedin listening? i’d sure like to see these things implemented. what do you think?

enabling web services

phil windley: enabling webservices
a well-written paper that offers 13 principles to follow.

  1. Every data record and collection is a resource.
  2. Every resource should have a URI.
  3. Cool URI�s don�t change.
  4. Data queries on existing resources should be done with a GET.
  5. Use POST to create new resources.
  6. Preserve the structure of data until the last possible moment (i.e. return
  7. Make XML Schemas available online for your XML.
  8. Make data available in multiple flavors.
  9. Use Metadata (RDF) for XML.
  10. Document your service API using WSDL, WRDL, or some other
  11. Advertise the presence of the data using WSIL.
  12. Adhere to data standards such as RSS where available.
  13. Use HTTP authentication as much as possible.

big words and small talk

New S# Language Adds Capabilities for .NET Developers

Innumerable pundits and programmers have pointed out the similarities between the most popular .NET languages (currently VB.NET and C#), and some like to focus on the relatively minor differences between them. S# is different. Not only is its syntax different, following the model of classic Smalltalks, but its underlying design and capabilities differ as well.
In 1999, Simmons was invited along with experts in 10 to 15 other languages, to join a then-secret project at Microsoft called Project 7 Lightning. Project 7 Lightening involved creating test implementations of these languages on the nascent .NET Framework code base to help Microsoft discover what features the framework needed to fully implement these languages in the future.

the .net platform (and by extension, mono) are getting more interesting every day. as more and more non-mainstream languages such as eiffel, scheme, haskell, ruby, python and now smalltalk get a .net port, the options increase. every self-respecting software engineer tries to learn several languages, but practicalities and a lack of a rich framework in the more research-oriented choices made this impractical in the past.
i am hopeful that we will see a day soon when there is a unified, cross-language and cross-platform class library. it wont be java, so my bets are increasingly on .net. in a perfect world, this library would incorporate CPAN, PEAR, and others. still missing: