And as I watched I started to record notes that I was going to publish here, but a bunch has already been said and I’ve read so much of it, so, I thought I would just hi-light a couple of the more poignant comments that I’ve read in all the hype from the last week.

My initial gut reaction was, okay cool, Google re-invented Lotus Notes and moved it onto the web for realtime communication and Joe Gregorio addresses this technically with his thoughts in “Wave Protocol Thoughts”:

Now some people have commented that Wave reminds them of Lotus Notes, and I’m sure with a little thought you could extend that to Exchange and Groove. The difference is that the extension model with Wave is events over HTTP, which makes it language agnostic, a feature you get when you define things in terms of protocols. That is, as long as you can stand up an HTTP server and parse JSON, you can create robots for Wave, which is a huge leap forward compared to the extension models for Notes, Exchange and Groove…

And speaking of these extensions, the opportunities are endless with an API that allows you to not only write “robots” in either Java or Python but host your own server to federate data (a huge enterprise feature).  And I actually thought the most impressive part of the demo was showing off a couple robots:

• “Rosy” a robot that translates text in realtime as you write, and 
• A spellchecker which also considered context before offering corrections.

If this becomes successful in the enterprise there is potentially a very large market of paying customers that want and will need extensions in every discipline from logistics to finance to marketing to manufacturing and beyond, not to mention all the data conversion that will also be needed.

However enterprise adoption and enterprise extensions are still years away.  I think the major and more immediate takeaway from the demo is that it increases expectations in web development.  I personally don’t believe it is quite as large as say, the way Google Maps changed the web landscape, that was a game changer and I believe Wave is more like a logical next step and Nick Gall highlights this in “My 2¢ on Google Wave: WWW is a Unidirectional Web of Published Documents — Wave is a bidirectional Web of Instant Messages”:

Here are a couple of my major take aways:

1. The Wave client is a major proof of concept (or pilot project) for HTML5. If the wave client becomes a killer app, it will have a major (negative) impact on other RIA architectures.
2. The Wave protocol is a major proof of concept for the extended use of XMPP. It transforms it from a IM/Presence protocol to a general purpose bidirectional streaming protocol.
3. Whether or not the Wave client succeeds, Wave is undoubtedly going to have a major impact on how application designers approach web applications. The analogy would be that even if Google Maps had “failed” to become the dominant map site/service, it still had major impact on web app design.

There are many passionate opinions on whether Wave will succeed or fail; but one thing is for sure, Google is gently pushing the envelope and therefore developers are expanding their knowledge of HTML5, ES5 and XMPP.  And, whether Google Wave succeeds, I think is irrelevant, because Google has demonstrated a glimpse of the future and when pursued with new technologies, everyone wins.  In that regard, Google Wave is already a success.

What’s Next – I Honestly don’t know and am perfectly fine not knowing. My career stalled during my time at CSC, I don’t know why exactly and while I do have some strong thoughts about it I’m not prepared to elaborate in detail at this time. However, I do know I need a change and it’s time to head a different direction.

NGC – My career started fast and I’d like to think very successfully at TRW/Northrop Grumman and there are a couple lessons/ideas that I often think about regarding my time there.

1. I built a solid name for myself there and had total say in what I wanted to do, by in large I had escaped the corporate bureaucracy and wholly controlled my own destiny. I greatly underestimated this benefit prior to my departure there.
2. 6 months or so prior to my departure I was offered a position that would have made me responsible for a nice chunk of revenue. I turned it down for many reasons, but the thing I did not really consider was how much the people who offered me the position believed in me. I regret not believing more in those who believed in me.

Commoditizing Software Development – During my brief time at CSC, it became apparent that Corporate America (or at least CSCs clients) is interested in commoditizing software development, and doing it through offshore resources in India. Personally I don’t believe it can be commoditized and doing so is a losing business strategy because not only does the quality of software suffer, but the “business” also suffers. If the work can be done in India for cheaper, so be it, but in my experience the quality is so bad, it is not worth the cost savings.

Fitness – I spent my 20s way overweight, I guess obese is the proper term. In the last 15 months I’ve lost 75lbs or so, others seems to notice the physical change. But, honestly I don’t so much. However, I do notice a mental change, and it is a huge one. It’s a major differentiator in why I am not nervous about being unemployed, I KNOW I am talented and I KNOW I will figure something out and be successful.

California/Ohio – I think it is safe to say while some good things have come of me moving back to Ohio, I wouldn’t be one bit surprised if I end up back in California, in fact I’d probably me more surprised if I didn’t. I miss it a lot, not sure if I’ll go back to SoCal or look for something new somewhere in the SF Bay area. Time will tell.

Python – I spent some time earlier this summer introducing myself to python. As I have said before something about python just seems right, and now that I have unlimited free time, I’m going to use it to hack some of my ideas together. I may also explore Scala.