As I sit in the CloudConnect Event at the computer history museum (twitter stream here), I was wondering about how to talk about cloud computing and the meaning of all this. It became clear to me when I saw the Paul Buchheit post today on “Communicating with Code”.
He writes (talking about his experience with the development of Gmail..)…“From that day until launch, every new feature went live immediately, and most new ideas were implemented as soon as possible. This resulted in a lot of churn — we re-wrote the frontend about six times and the backend three times by launch — but it meant that we had direct experience with all of the features. A lot of features seemed like great ideas, until we tried them. Other things seemed like they would be big problems or very confusing, but once they were in we forgot all about the theoretical problems.”….”The great thing about this process was that I didn’t need to sell anyone on my ideas. I would just write the code, release the feature, and watch the response. Usually, everyone (including me) would end up hating whatever it was (especially my ideas), but we always learned something from the experience, and we were able to quickly move on to other ideas.”
What we have here is a real time web waiting for real time code. All of the discussion about cloud computing is really about rapid development,provisioning of resources..etc. – in the end a better product for users (hopefully). Paul talks about this in his post -Gmail turned out pretty good.
Cloud computing allows developers the ability to get “stuff” up fast. Speed and feedback is critical to success and more important than having some “hardened app” that no one wants. This is only way to develop in the web today. Success is about speed and product acceptance is dependent on that speed which drives relevance. Build a great product and it will work.
The motto “build it they will come” is irrelevant. Instead the motto today is “Build it because they are there already”. Having a robust, easy to use, easy to provision, and reliable cloud and services will flow to users for critical feedback The rest will take of itself. The good apps and services will “come to us” – Welcome to Infrastructure 2.0.
discussion on twitter via tag #cloudconnect