Lesson learned?

In the last months I've had several times a dejavu feeling. All this web2.0 noise is starting to sound more and more like the .com thing nine years ago.

On one side, it is a little bit deceiving: am I so old to tell yarns and anecdotes about how insanely money was made and lost those days?. But looking at the past is also a good way to reflect on what is going on, and question whether past lessons have been learned...

All these thoughts come because I've just read an article on the Lessons from the Las Bubble, and I found some of the ideas really interesting.

One of the best points is when the authors talk about network externalities and exponential growth. They rightly point out that the fact that you have an internet based business model does not imply that you are going to have network effects. Network externalities are not about the technology you use to build your service, but about the way users use it and value the social network that is build on top. And that was one of the mistakes repeated over and over again in the .com era. There are no network externalities to draw from in a internet based retail store, as there are no network externalities in setting up a brick and mortar retail store.

But that should not be a problem for Web2.0, isn't it?. Since Web2.0 is all about social networking, that mistake will not happen again: we are definitely going to have network externalities and, consequently, exponential growth. Wrong!!!

The fact that some of the technologies collected under the Web2.0 name enable the formation (I should say the facilitation) of social networks does not mean that any venture in the Web2.0 world is going to build one. It is not about social networks, it is about the value of they provide to users.

There have been lots of serious studies on how social networks are formed, used, and, at the end, valued by people. Social networking is a natural human activity, not something that was invented a couple of years ago by MySpace or Flickr. The fact that these two business (and a few others) have been very successful at using the human tendency to interact with other people to extract an economic profit does not mean that any venture that talks about network externalities in its business plan is going to be as successful and profitable.

When technological jargon becomes mainstream

It is very common that during the process of development of a new technology, an specific jargon is created. When the technological innovation starts to get deployed, the jargon acts as a symbol to differentiate those who know about it. But as the new technological features become mainstream, and with some good marketing help, the jargon words detach from the original technical field and get incorporated into the consumer language.

That evolution is specially visible in technologies related to consumer products (how many people who look at the L2Cache size spec for microprocessors has an idea, beyond bigger number is better, about the meaning of that spec?). But in certain circumstances this jargon evolution can also happen in other technologies not so consumer oriented.


In Bangalore, the major center of the software export industry in India, in an environment with a very high IT employment demand, IT and programming related skills becomes a very valuable asset. The consequence is that the programming jargon is becoming part of the regular language. Small signs advertising training in very specific programming technologies abound, and, in certain situations, it is quite easy to start a conversation with an stranger about specific programming languages, platforms, and techniques.

Web 3.0 (?)

Web2.0 has become the big buzz word of the year.

Reading certain news and hearing some people talk, it seems that we are back in time to 1999, but with tagging and social networking substituting portal and e-commerce as the bright ideas that will change the world, and make (some of) us very rich. Web2.0 has its new heroes (the googles, the flickrs,...) and villains (guess who...). And obviously, there are the pundits that talk a lot about it and create all the hype, and in some cases make a lot of money out of it.

But, we cannot say that we did not learn our lessons: the Web2.0 bubble may explode as the .com bubble did a few years ago, so it is better that we have a new concept ready when this happens: an the term is, obviously, Web3.0.

Web3.0 is just a fancy name for a concept that has been lying around for a few years: the semantic web. I guess that the term semantic web sounds too geeky to attract venture capital, so somebody came up with the fancier Web3.0, and then, publications such as the MIT Technology Review have picked it up, so it is becoming mainstream in the internet and technology related circles. According to Nova Spivack, blogger and founder of one startup using semantic web technologies, there is even a Web4.0 waiting somewhere in the future...

But besides all the naming fireworks, there is a more subtle issue around the concept itself of an intelligent (as in artificial intelligence) network. I've already talked about the goods and bads of the collective intelligence that some of the new internet based technologies enable. The underlying question is how much intelligence are you ready to outsource to somebody else, be it some artificial intelligence search engine, be it the collective seating somewhere in cyberspace or, most probably, a combination of both.

It is obvious that any technology, and Web *.0 is not an exception, embodies in its design lots of cognitive and social assumptions and when adopting those technological artifacts we are, up to a certain extent, adopting those assumptions. And that is fine if you are aware of what are those underlying assumptions and what do they mean for you.

An example with serach engines: although Google's page ranking algorithm is kept as the company's major trade secret, it is well known that it is somehow based on the number of pages that link to a certain page, so, when I'm using Google as a search engine, I know that I'm actually looking, more or less, for the most popular pages about something, and hope that the most popular are also the best. But of course, that is not always the case, so it is nice to have other search engines that are based on other criteria and even a different search space (some of them provided by Google itself, like Google Scholar for research papers).

At the end, I end up using different search engines for different things, and I guess that the Web3.0 response to it would be building some kind of intelligent agent that can embody part of the criteria I use to select between the different criteria embodied in the different search engine options. The only problem I see is that somewhere in this chain of building intelligence on top of intelligence there must be some place left to personal, private, options and criteria.

I have to admit that I have not digged deep enough in the semantic web theories and technologies to understand how personal option and individual difference can be implemented in a way that is also easy to understand and use. But it is also true that I have not seen this issue addressed by any of the Web3.0 visions and predictions I have seen so far. So, at least for the time being, I will remain in the skeptic side about Web3.0 and I'll be, at least, a little reluctant to outsource the small portion of intelligence I have left to some unknown agent...

Web 2.0 ... The Machine is Us/ing U,

It seems that Web2.0 is the buzzword of the moment. Everybody is talking about it, and, as usually, lots of nonsense is being said, as people try to seem smart and proof that they know better, specially when talking about how Web2.0 is changing all types of social relations (and how they know the best way of making money out of it...)

That is why I find this video interesting. It is well done, goes straight to the point and it is thought provoking. It does not try to define what Web2.0 is (I don't think anybody really knows what it is...) but points out some of the changes that new web based technologies may bring and the controversies that they generate.