Posts tagged linkedin
Apache Hadoop
Nov 26th
Apache Hadoop presentation which I gave at my workplace. Its a beginners guide for developers.
GWT vs Java vs C
Aug 3rd
They say history repeats itself. Here is an instance where it happened twice.
The “C” Days
In the days of 8086 and MIPS there were different types of instruction sets for different processors. Due to this programs written in assembly language for one processor could not run on another.
The “C” approach came in as a gospel, where in the programmer can write code in one language and compile it to any instruction set. This revolutionized the computer industry in the 1970s-80s, and we saw millions of lines of code written during this time.
The “Java” Days
Then during the 1990s the same problem manifested in a different form. This time there was a different verity of Operating systems. The “c” code could not keep up with the different flavors of underlying OS operations and quickly writing ubiquitous code became a herculean task.
This is when smart folks at Sun rewrote history and invented Java. The concept was same, write code in one language then compile it such that it can be run on different platforms (OS). Though there is a slight variation, this time the compiled code runs over a Virtual machine which wraps the underlying platform. This virtual machine in turn takes care of platform variation.
The “GWT” Days
As we said earlier, History has knack of repeating itself. Now in 2000, our industry is moving towards the client server architecture. JavaScript is the leading technology for writing the rich clients these days. Many frameworks have sprung up which tries to make JavaScript development fast and easy. But again all these frameworks face the same issue as did java and c. JavaScript can run on different browser IE, FireFox, Google Chrome and many more. All these browsers have different implementations of JavaScript which cause a nightmare for developers.
Enter GWT (Google Web Toolkit). The concept is same again. The code is written in Java and its is compiled to Java Script. All the nitty-gritty’s related to browser is taken care of by the GWT compiler. This technology was released by Google around mid 2006 and it has come a long way since then. Its much stable and production ready. GWT is on its way to become a force similar to C and Java.
Conclusion
These are few designs which are so powerful that can alter the course of history. The compiler is one such thing. We have seen it revolutionize the IT industry time and again. This time it’s taken the form of GWT. As developers, it’s high time that we look upon this technology closely and prepare ourselves for the new future.
Crossing the Chasm
Mar 23rd
Today I gave my 2nd Toastmasters speech “Organize your speech”. I choose the topic “Crossing the Chasm”. It was based on the book written by Geoffrey A Moore, “Crossing the Chasm”. The following is my speech.
Crossing the Chasm
Opening
How many of you dream of starting your own company some day? How many of you want to be the CEO of your own firm? I know deep down in our heart everyone of us have the secret desire to do just that.
Today I am going to talk about the book “Crossing the Chasm”. A must
read for all the Startup aspirants. This book was written by Geoffrey A Moore in the year 1990 and sold about a million copies since then.
So what is this book all about? This book outlines a set of problems faced by all the startup and identifies certain well defined
solutions.
Let’s jump in without much ado. I know all of you are dying to hear more about it.
Body
The Bell Curve
To identify the problem w let’s look at this diagram here. The Bell curve the parabola. The market scope of a product can be defined by this cure. At the front are the innovators, the folks who invent the product. They are the first user of the products. Closely following them are the Early Adopters. These are the folks who use the early version of the product and give their views. Then comes the Early and the Late majority of the user. This user base is the major chunk of the user base. And for a product to be successful the product
managers have to position their products to this section of the curve.
The Chasm
We often think that all these user groups are connected. And once we start selling a product it will quickly spread across the curve via
word of mouth. But that is not the case. There is a major problem gap between the 2 groups the early adaptors and the majority. The Chasm. The problem is that the majority group uses only those products which are already used and recommended by other folks in the majority curve. They cross reference each other. A classic case of Catch-22. The majority will use only those products which are already used by the majority. So how can we get them to use a new product? That is the chasm.
Movie Example
Let me give you a real life example. Take the case of the movies. The director, actors and the producers are probably the first people who see the movie. They are the innovators. When a movie is released we have the college students who don’t have anything else to do. They see all the movies. They are the early adopters. But for the movie to be a hit the general public has to see the movie. People like you and me. But I won’t go to see a movie unless my friends tell me it’s a good movie. And they won’t go to the movie if I don’t tell them that it’s a good movie.
The D-Day Analogy
Now that we have identified the chasm, let’s see how Moore solves them. Moore gives a brilliant analogy to explain the solution. The D-Day analogy.
During World War II, Hitler had captured most of Europe and the allied forces wanted to get a foot hold in Europe to launch there invasion further. So on June 6, 1944, the allied forces launched a massive invasion and landed on the beaches of Normandy. About 2 lacks troops were involved in the war. Once the allied forces setup their base in Normandy they could go further and capture other parts of Europe and eventually defeat Hitler. This day June 4th of 1944, is referred to as the D-Day in history books.
In his analogy, Moore refers to Britain as the Early Adopters, The English channel as the Chasm and Europe as the Majority. Moore suggests that to get to the majority group we should identify the point of attack (a weak point which is overlooked by the competitor) and put all our force to capture it. Once we have become the market leader in the inch we can go ahead and invade other portions of the market.
Point of attack
Let’s dig deep into the solution. Firstly let’s see how to indentifying the point of attack. Every market can be segmented into smaller groups. Once we have segmented the market, we can identify the segments which are not well served by the competitors. See if the segment has certain pressing problems which can be addressed by the product. Let me give you some examples.
Blog Example
Let take the case of blogs, we want to start a new blog and want to make it very popular. Clearly we can take over the established players, we can write about the same things the established players are writing about. Lets take the technology space. There are many blogs, Meshable, GigaOM.. etc. which are well established. We can start a blog which writes about a specific technology inch. That is what Cloud Avenue did. Its concentrated on cloud computing and it’s a popular blog now.
Postit Example
Another example is the case of Yellow Post Its. They were first manufactured by 3M. During the initial days no one used them and the product was not doing well. The product had hit the Chasm and 3M was going to shut it down. That’s when a dynamic Product manager hit upon the idea. He sent packs of Post It to the secretaries of all the Fortune 500 companies. The secretaries used them to scribble agendas, send memos and note phone calls. And the rest is history.
Assemble the Force
Once we have identified the point of attach we can assemble our force and start the attack. So what do we mean by Assembling the force. When we are selling a product it does not end with there. It has much more to it. We have to identify the packaging which will suit our target audience. The product may be complicated so we might have to provide training. The product might need supporting products. Moore calls this the whole product.
Oracle Example
Oracle databases as a whole product. When a company decides to by oracle product it actually buys a whole lot. It also buys after sales support. The company has to buy more software to manage the database. Plus additional software to access the database vie the application layer. Apart from that it might have to provide training to it employees. Oracle has solved all these problems very efficiently, it delegates the training stuff to third party and the oracle database access is done by open source community and oracle encourages these efforts. Oracle collaborates with its subsidiaries to develop products for managing the database. And that is the whole product.
Launch the Invasion
Once we have identified the Point of Attack, and Assemble the Force it’s time to launch the invasion. This is where we think of distribution and pricing. According to Moore, in a battle distribution is the vehicle and pricing is the fuel. Moore dwells deep into these topics in the book. But they are out of scope at this juncture. You can read more in the book.
Conclusion
Let’s recollect what we learned so far. Every product has a market scope which is represented by the bell curve. At the front of the curve is the innovators and the Early adopters and at the middle of the curve is the early and late majority. For a product to be successful it has to be used by this majority group. But there is a chasm between the two groups.
To cross the chasm we have to identify an inch in the majority market which is not addressed by our competitors and put all our force in capturing it. Once we have that we can target the other portions of the majority market.
For all the startup aspirants, I highly recommended that you read this book before you plunge in. I bought it on eBay for Rs. 230. It is a worthwhile investment.