Sorry, been too busy in the last weeks. Will see if I can improve on posting frequency, too many things pile up. But here we go:
New York Times (registration required): Meetings Are a Matter of Precious Time True, so true.
Waferbaby asks people “What do people use to get the job done?” Insights from John Gruber (daringfireball.net), Alex Payne (Twitter) and others. Interesting.
Dare Obasanjo discusses an important difference: Platform as a Service vs. Utility Computing.
- Utility Computing: In this approach, a vendor provides access to virtual server instances where each instance runs a traditional server operating system such as Linux or Windows Server. Computation and storage resources are metered and the customer can “scale infinitely” by simply creating new server instances. The most popular example of this approach is Amazon EC2.
- Platform as a Service: In this approach, a vendor abstracts away the notion of accessing traditional LAMP or WISC stacks from their customers and instead provides an environment for running programs written using a particular platform. In addition, data storage is provided via a custom storage layer and API instead of traditional relational database access. The most popular example of this approach is Google App Engine.
As it stands today platform as a service offerings currently do not satisfy the needs of people who have existing apps that want to “port them to the cloud”. Instead this looks like it will remain the domain of utility computing services which just give you a VM and the ability to run any software you damn well please on the your operating system of choice.
However for brand new product development the restrictions of platform as a service offerings seem attractive given the ability to “scale infinitely” without having to get your hands dirty. Developers on platform as a service offerings don’t have to worry about database management and the ensuing complexitiies like sharding, replication and database tuning.
An important distinction if you ask me and a clear crossroad if you want to go into cloud services.
If you want (or have) to enable a web-application with offline-capabilities, Google Gears is often the tool of choice. Eduard Martini gives some good insight on O´Reilly InsideRIA: Google Gears—A Great Tool to Enhance Web Applications. Recommended.
Jeremiah Owyang, Senior Analyst at Forrester gives a great overview of the Social Network Industry on his private blog: Weekly Digest of the Social Networking Space: Jan 21, 2009
And Nicole Simon explains why LinkedIn will fail in the german market: Linkedin taking the traditional approach in Germany and why that will fail (as usual)
Most of the time, they just make a translation and try to tell everybody how awesome they are everywhere else, as if this is enough.
Jason Scott: Fuck the cloud:
So please, take my advice, as I go into other concentrated endeavors. Fuck the Cloud. Fuck it right in the ear. Trust it like you would trust a guy pulling up in a van offering a sweet deal on electronics. Maybe you’ll make out, maybe you won’t. But he ain’t necessarily going to be there tomorrow.
Yeah, you should know where to place your bets. And backup is not for the fainthearted only, also real men do backups (off the cloud, in this context).
Whoever wanted to know how David Allen gets things done, here a movie on Youtube (via):
TPI has also a german blog now, from the office in Frankfurt.
Garr is great to find (and comment on) extraordinary presentations. This time: Bill Gates at TED 09: How do you make a teacher great?
TED is the best and most inspiring conference series in the world, if you ask me. Fantastic speakers, great presentations. Awesome.