What I'm Reading, July 22 2011

KKline — Thu, 21 Jul 2011 14:43:00 GMT

I read too much, and that, my friends, is an entirely separate topic for a blog post. But I thought I'd share with you a little more about what I'm reading because sometimes, if I'm lucky, it might be something you'd enjoy too. So I'm going to start sharing what I'm reading at least once per week, partly so that I don't firehose too many reading links directly into your brain (where I to do it say once per month) and partly to solidify in my own mind the information that I'm reviewing. So here are a few good links for the seven days leading up to July 22, 2001:

Microsoft and Whitehouse partnership on BigData: BigData isn't a particularly new concept. But I was intrigued to learn that the National Science Foundation, Microsoft, and 13 other teams were partnering on developing better BigData analytics for lots of government data from activities such as healthcare, economic development, education, transportation, and the power grid. Cools stuff! Plus, Microsoft has developed a new tool called Project Daytona to better harness the power of the cloud, in general, and Windows Azure, specifically.
While we're on the topic of Federal IT in the Cloud be sure to read this linked article from ComputerWorld. Say what you will about our government, but putting government IT in the cloud and increasing both its transparency and availability will make a huge difference in how the Federal government will be able to service the public. We're talking as big a difference as corporations experienced between the "catalog on the web" experience of the 1990's to the Web2.0 experience of today.
If you're the social media type, give this article a read discussing the Power of Hashtags in Social Media.
The Register, of the UK, whose tagline is "Biting the hand that feeds IT" has a great article on a spat over database technologies between the IT sage Michael Stonebreaker and Google. It's a great read if for no other reason than to prove that databases are worth fighting over.
And if you think Microsoft is still towing the relational database barge without thinking about other technologies, you need to read up on Projects Dryad and Daytona.
Finally, I'm still getting lots of questions about when and where to limit SQL Server's Max Degrees of Parallelism. Be sure to read Microsoft's Recommendations and Guidelines for 'max degree of parallelism' configuration option here.

And just because so many of us in IT are closet or former musicians, there's Live Guitar Lessons with Steven Krenz, sponsored by my hometown boyz at Gibson Guitar. Got a favorite article or tool tip? Let me know! Enjoy,

-Kev

Follow me on Twitter.

Google Wave is Dead! Long Live the Wave!

KKline — Tue, 10 Aug 2010 23:16:00 GMT

I Never Could Hang 10 (Minutes) on Google Wave

http://bits.blogs.nytimes.com/2010/08/04/google-kills-wave-its-collaboration-tool/?ref=technology

Even if you don't read the article, you can see from the URL that Google has decided to put an end to the collaboration experiment known as Wave. Wave will be available through the end of the year and most of its major components are now available as open source, should any devotees choose to continue developing the code base. However, Wave didn't reach the critical mass that Google was looking for and, without that critical mass of users, it wasn't seeing a lot of innovation or updates to the features or UI. I view Google's reach of 1M users as a "failure" with a bit of grin. How many other vendors out there would consider 1M users too few? Otoh, if they wanted really wide adoption, why in the world did they require a private invitation? Superior products are frequently hampered by inferior marketing and market delivery, this being a really good example.

Slide to the Rescue?

Great Idea Leads To Great Product Success, Right?

The Graveyard of Ideas

I also feel that Google Wave is a good example of a technological solution looking for a problem, as well as a product looking for a marketing message. When launching a product, it's crucial to have a crystal clear message to a well-defined audience. Any ambiguity in the message or muddling of the audience can spell doom. And, IMO, Google clearly missed the boat on both counts. Many of their demos were all about sharing photos. Uh, ever heard of Facebook, n'est pas? Then again, many later PR was about collaboration. Then how come we didn't get smokin' hot project management demos? A book that I recommend called The Innovator's Prescription (website is here) says it very well:

"The graveyard of failed products and services is populated by things that people *should* have wanted--if only they could have been convinced those things were good for them. The home-run products in the marketing hall of fame, in contrast, are concepts that helped people more affordably, effortlessly, swiftly, and effectively do what they already had been trying to get done." (Christensen, The Innovator's Prescription, p. 16)

I really like Christensen's point. So many people who build products focus on the "should" of a product, as in "this should make a lot of people happy", over and above providing an effortless aid to people's daily tasks. This leads me to a topic for another day, user-interface design. But enough writing for now. It's bed time.

So what are your thoughts? Do you think other factors contributed to Wave's decline?

Thanks!

-Kevin

Twitter @kekline

[caption id="" align="alignright" width="305" caption="I Never Could Hang 10 (Minutes) on Google Wave"][/caption]

While enduring an endless series of flight delays and disgruntled passengers in the Baltimore airport that was my own personal travel hell on the evening of Thursday, August 5th, I came across this interesting and important article: http://bits.blogs.nytimes.com/2010/08/04/google-kills-wave-its-collaboration-tool/?ref=technology Even if you don't read the article, you can see from the URL that Google has decided to put an end to the collaboration experiment known as Wave. Wave will be available through the end of the year and most of its major components are now available as open source, should any devotees choose to continue developing the code base. However, Wave didn't reach the critical mass that Google was looking for and, without that critical mass of users, it wasn't seeing a lot of innovation or updates to the features or UI. I view Google's reach of 1M users as a "failure" with a bit of grin. How many other vendors out there would consider 1M users too few? Otoh, if they wanted really wide adoption, why in the world did they require a private invitation? Superior products are frequently hampered by inferior marketing and market delivery, this being a really good example.

Slide to the Rescue?

[caption id="" align="alignleft" width="320" caption="More Fun than Google Slide?"][/caption] I also feel the need to point out that I have a lot of respect for Google giving the old heave-ho to a product that needs to go. Many companies cling to a great idea, funneling huge amounts of resources into what everyone else can see as a black hole. Failure, under vibrant and forward thinking leadership, is only success delayed. Read Google's take on the situation here. Certainly, this means we'll see Google pushing their new social media acquisition, Slide, much more as well. And, since many of the technological bits of Wave will live on, I'm sure we'll see Slide advance in interesting ways. Frankly, I found the general idea of Wave to be fascinating and powerful. But after spending quite a bit of time, like at least 20 minutes, tinkering around with it, I still had no idea how to do anything with it. I was so motivated to use it that I almost watched one of the videos that they'd posted to train you. But honestly, am I just ridiculously jaded or has the overall market for cloud-based apps moved the bar for ease-of-use that anything that takes more than 15 minutes to figure out is drama? I hate to say it, but I think the answer is a resounding "YES". By extension, I think that this is the main reason that email still trumps all other methods of collaboration. (Yes, that includes Microsoft SharePoint too for all you fanboys.) That is, email does not disrupt any existing workflows, it has a clean UI, it doesn't make you learn new ways of working, and it's so widespread that you're not hampered by a product that has a very limited user base.

Great Idea Leads To Great Product Success, Right?

[caption id="" align="alignright" width="341" caption="The Graveyard of Ideas"][/caption] I also feel that Google Wave is a good example of a technological solution looking for a problem, as well as a product looking for a marketing message. When launching a product, it's crucial to have a crystal clear message to a well-defined audience. Any ambiguity in the message or muddling of the audience can spell doom. And, IMO, Google clearly missed the boat on both counts. Many of their demos were all about sharing photos. Uh, ever heard of Facebook, n'est pas? Then again, many later PR was about collaboration. Then how come we didn't get smokin' hot project management demos? A book that I recommend called The Innovator's Prescription (website is here) says it very well:

Search results matching tags 'Tools', 'News Analysis', and 'Cloud Computing'

What I'm Reading, July 22 2011

Google Wave is Dead! Long Live the Wave!

Slide to the Rescue?

Great Idea Leads To Great Product Success, Right?

Slide to the Rescue?

Great Idea Leads To Great Product Success, Right?