Jeff Nolan left SAP recently and joined Teqlo.
The fundamental problem that has bedeviled application developers is that they are fundamentally disconnected from the people who use their applications. They have design partners and focus groups, beta periods where feedback is channeled back to the developers and tweaks made, and there are post-release initiatives aimed at improving the quality and satisfaction rate of the product but even in the best run process the users are not intimately involved in the development process. With Teqlo the users are intimately involved because they are the developer.
To expect that users, even power users, will be able to build applications that stitch together web services from multiple vendors is a stretch. Teqlo isnt attempting to build a new development language like Ruby on Rails that dramatically lowers the barrier, what we are doing is essentially reverse programming. Were treating development as a data flow problem, not a programming flow problem. If there is a core piece of technology that we have invented, it is the routing methodology and not the semantic definition of components; Teqlo takes web services that are wrapped up as components, we call them Teqlets, and determines the optimal sequencing based on the data inputs/outputs of each component. Yeah, its hard and there is a lot more to it than I am revealing here, but the point of this post is not to talk about our technology but rather what it means for users.
Dan Farber has more.