If Google needs so many people to work on its to-do list, why is it putting so many barriers in front of its "Help Wanted" portal? The answer is that the company would rather turn away a dozen people who might have worked out than hire just one who turns out to be toxic to the organization. As JotSpot CEO Joe Kraus notes in his entrepreneurship blog, Bnoopy, "A players hire A players, B players hire C players, and C players hire losers. Let your standards slip once and you're only two generations away from death."
Should this be the doctrine that informs a Web services marketplace? Is it better, when searching for service candidates, to reject a dozen might-have-beens rather than letting a single unsatisfactory candidate get through? We talk about a vision of Web services enabling a dynamic marketplace of changing needs and competing service offerings, instead of being merely a standards-based technology of static application integration: Are we going to "hire" services in the highly selective style of a Google or, for that matter, a Microsoft? Or are we going to come up with mechanisms of identifying, evaluating, and qualifying and rejecting candidates that are continually open to new entrants?
This seems like an important question, as such major Web presences as Amazon join Google in the competition for the role of next-generation application platform. Amazon itself is building on its own services foundation to enter new markets, as well as offering that foundation to others. The next generation of the Web, it's clear, is going to be defined by the competition among different ways of delivering on this vision.
Good thought worth pondering.