TechnoMagicians Blog

I had a lot of respect for Ray Ozzie until I read this article titled “Google Wave anti-web”

It seems that Ray has been drowned in the Microsoft Cool-Aid and has been assimilated by the MS Borg.

Ray Ozzie created Lotus Notes and Groove. Two very well respected and useful collaboration tools. However, a number of statements he makes in the article are just absurd.

First the anti-web statement. No idea where he is coming from here. There is nothing anti-web about Google Wave. They are using open standards, open source and I believe the whole damn thing works in a web browser. How is this anti web?

Second, he says “Ozzie said the open web relies on open data formats and protocols, not opaque packages and payloads being tunneled across the web”. Well, Wave is based around XMPP protocol which is an open web standard.

Third, I have no clue what he is trying to say here: “He did not explain exactly how he believed Wave to be complex. Instead he suggested that Wave would rely on open source - because without it, Google’s collaboration platform would be too complicated for those outside the company to implement.”

Fourth he says “”Google Wave and Mesh are basically the same thing”. That is another ridiculous statement. If you look at the Wave beta and the Mesh beta you won’t see much at all that is the same. All I see Mesh doing right now is syncing files. (perhaps the full release will do more). Not very exciting and hardly anything to do with real-time collaboration at all. Lets get real Ozzie.

So, to sum up, I’m with Brent on basically saying that Ray Ozzie is irrelevant. To quote Brent Ashley via IM message: “but yeah, I’m afraid Ray Ozzie is  no longer relevant after that”.

You would not think that the most used tool of a poker player would be Twitter but it seems that is the case these days especially since the WSOP (World Series Of Poker) is well under way in Vegas right now and goes for another 5 weeks or so. Just about every poker pro and any other poker player are using Twitter to update their status during tournaments with their chip counts, hands and other miscellaneous stuff going on.

Poker news outlets are also using Twitter to get their updates out and they are building sites and tools around Twitter. For example, see PokerRoad Nation (#nation).

PKR Poker is live streaming a lot of the action that will not be televised and they stream Twitter messages across the screen that are sent to their address (@WSOPLive).

PKR Live Stream

Here is a feed of some Poker tweets:

I’ve been reading what I can about Google Wave and it looks to have some really nice features for collaboration on so many different levels. I’ve missed a real collaboration tool since Groove was purchased by Microsoft. I used to use Groove on a daily basis with a number of different people and different projects to collaborate effectively. The problem we always had with Groove was that its data store was proprietary and it was difficult to get things out of it when needed. When Microsoft purchased Groove Networks things seem to stagnate and we stopped using it regularly to the point where I only open it maybe once or twice a year for the past few years. For all I know Microsoft has made some improvements to it in their 2007 version but I never bothered looking. It just became an old rusty tool we no longer bothered to want to use again. The only reason I still keep it around is I have data in there I reference every now and again. Somehow I have to extract it and uninstall that application!!

I think Google Wave will definitely pickup where Groove left off. The fact that it will be an open system is fantastic. The reason they are announcing it early is that they want developers to start creating apps with their API for it now so that a ton of stuff is available for when it is released.

You can get an idea of how I guess folks can add on to Wave through the API during their demo of spell checking, linking and searching. They may have just redefined how spell checking works as well. Basically it looks at your potential spelling mistake by the context of the word. Very nice.

Alexander van Elsas has a good list called “10 reasons why Google just reinvented online communication“. Check it out.

This presentation is well worth watching from Google IO even though it is over an hour long.

Ever since I picked up an Apple iTouch (iPhone) I immediately knew Apple had to make a tablet sized device.

The reality has been coming closer and closer with the various rumor sites announcing various things. The latest is right along the right lines Apple should be heading down. And hopefully they are. If only they could get there sooner so that I don’t have to wait around to purchase the thing.

Also see this post and this post.

The folks at Digg have come up with what they are calling Multipart XHLHttpRequests (MXHR). Basically it is a method for bundling multiple HTTP requests into a single HTTP request and unbundling on the client side through a Javascript handler.

As described by the Digg’s blog post:

We call this technique MXHR (short for Multipart XMLHttpRequests), and we wrote an addition to our Digg User Interface library called DUI.Stream to implement it. Specifically, DUI.Stream opens and reads multipart HTTP responses piece-by-piece through an XHR, passing each chunk to a JavaScript handler as it loads.

Why do this? Well, DUI.Stream will allow developers to drastically improve the speed of uncached page loads by bundling most of their resources into a single HTTP request, with a single time-to-first-byte and no request throttling by the user agent. Additionally, the size of the response has no effect on the rendering time of each chunk, as the client handles each piece of the response on the fly and can inject it into the DOM for rendering immediately, in the exact order you specify. On a high traffic, high-activity site like Digg, we have to display incredible amounts of data on each permalink — typically hundreds of user images within the first 50 comment threads on a page alone, not to mention the UI chrome and actual comment data. (You can see this for yourself: notice the number of HTTP requests that queue up when you expand a page of comments). So our primary use case for DUI.Stream is turning that first long, arduous page load on an empty cache into something nearly indistinguishable from a page of data with fully cached resources.

Try out the 2nd demo with the images to really see how this works.

The most popular game for all of the 90’s has just been released for the iPhone. Myst by Cyan. This is a perfectly suitable game for the iPhone interface. I predict that this will quickly rise to the #1 selling game on the iPhone for a whole new generation of folks. I can’t recommend it highly enough. It might be one of the first and only purchases I make if and when I get an iPhone. It will bring back fond memories exploring the “ages” again.

Myst was the best selling PC game since released in the early 90’s until The Sims in 2002. And it remains as the best selling adventure game to this day.

Myst was so popular that it helped drive adoption of the CD-ROM. It must have been one of the first games produced on CD-ROM.

Myst was created by, in my opinion, the genius brothers Rand and Robyn Miller.

Cover It Live (www.coveritlive.com) is a new tool that you can add to your website to enable live blogging. Basically a much more advanced BlogChat. Other features include publishing pictures, video, and email. Instant replay when the live event is over. Not sure what other features are available as the website isn’t that great at pointing things out and I can’t be bothered to investigate any further.

Looks like the Google GMail team is doing some interesting things with HTML5:

The HTML5 draft adds a lot of exciting functionality to browsers. Perhaps the most exciting is adding a way for websites to be launched offline. For devices that have a high bandwidth and highly available connection, offline functionality might not be so important. For web applications running on mobile devices however, being able to launch offline can dramatically improve the web application experience.

AppCache support on the iPhone is still under development, but as of firmware 2.2.1, it is usable.

via Google Code Blog: Gmail for mobile HTML5 Series: Using AppCache to Launch Offline - Part 1.

I agree 100% with this so am reposting the entire blog post here from GigaOM. Microsoft always used these techniques and I always thought it was one of the worst methods of conducting an interview.

If Sergey Brin applied for an engineering position at Google today, would he pass the requisite phone screening? Don’t be so sure: While he might look good on paper, he’d probably have to brush up on his Python programming skills first. Even if he passed, would it tell his potential employer anything useful about the value he could bring to the company?

Most engineers are familiar with the initial phone interview: a short, technical interview prepared by the prospective employer, and used to verify that the programmer meets the minimum technical qualifications of the job. Lots of employers think these screenings are a quick way to weed out bad engineers, but personally, I refuse to do them. Here are three reasons those looking to hire the best engineers should reconsider the “phone screen” interview altogether and jump right to a full-length phone or in-person interview:

1. Recruiters and other non-technical people typically don’t understand the questions they ask, and that leads to a one-way conversation. In addition, questions are often stated incorrectly, or without the originally intended context and as such suffer from lost-in-translation syndrome. Correctly evaluating a candidate over the phone takes longer than a typical “screening” interview, and should be done by equally tech-savvy individuals on the employer’s side.

2. From the perspective of an engineer, if an employer asks a lot of trivial coding or algorithm questions, it usually means the job they’re hiring for isn’t going to be that interesting (activate the big-company-coding-job radar). Phone interviewers do occasionally ask deeper questions, but given the limited time of a screening interview, and the inability of a candidate to present code or design diagrams, they are often forced to ask trivial ones.

3. Intelligence assessments can be a good indicator of talent, but don’t waste time asking them to solve puzzles pulled off the Internet: Look at SAT or GRE scores, school transcripts, or some other substantial proof of intelligence (or lack thereof). This kind of background on a candidate can usually be found without the need for a phone interview.

Only good engineers can accurately measure the skills of other good engineers, and it takes a lot of probing in an in-person, back-and-forth conversation to get there. A meaningful engineering interview has to be conducted in person, with multiple engineers, and over the course of several hours (if not an entire day). It’s worth the effort.

via Looking to Hire an Engineer? 3 Reasons to Forgo the Phone Screening.

When I first heard of this I dismissed it as I thought they were talking about the demise of email due to Twitter. That would be a ridiculous notion. However, after getting into the presentation further, (found here) I realized Daniel Sandler might be onto something.

From the BirdFeeder website:

Birdfeeder is the prototype implementation of a RESTful, interoperable, Internet-scale microblogging protocol, tentatively called Fethr (Featherweight Entangled Timelines over HTTP Requests).

Although this would need some traction to really get going. Look at Instant Messaging. How long has it been a great tool for communication and still there is little to no interopability between the various systems. Only Google / GTalk and a few others have adopted XMPP so that there is the possibility of interopability. The big guys, ICQ, Yahoo, MSN, AIM still haven’t bothered to interoparate much if at all.