This may not sound like a big deal, but if you're a book editor or a journalist, and you have spent countless hours moving your documents to Google in order to collaborate in real time and track revisions, (not to mention teaching authors and others how to use G Docs) then you are probably standing on a chair in your office with a noose around your neck and wondering whether or not to jump.
I cannot believe that such an intelligently run company would do something so stupid, but then I have also been a MicroSoft customer for over twenty years so what should I expect from companies run by engineers who don't have a clue about why we customers buy their software.
Could we be buying it because we think it will help us get real work done? What a concept! I guess if I were an engineer, I would have trouble with it, too.
Showing posts with label google. Show all posts
Showing posts with label google. Show all posts
Tuesday, April 27, 2010
Saturday, November 14, 2009
I'm on Google Wave, finally
I requested invitations from Google several times, with no response, but then last week I got irate and told Google that I was their ideal tester, since I live in email and communicate with co-workers and customers in North America, Europe, Asia and Australia. A few nights later, the invitation arrived. I got it on my Blackberry as I was walking from the gym back to my car, after work. Needless to say, I cut short my evening activities so I could get back to the office and join the Wave adventure.
Being a careful sort, I worked my way through LifeHacker's book on how to use Wave before I actually logged onto it. Once onto it, I could see it was completely different from what I had hoped for. I was looking for a way to integrate my online communication, which comes in via email, chat, SMS, Twitter, FB, etc., so that even though I have the ultimate email-based GTD system in place, there are a lot of messages (meaning tasks and projects) that have to happen outside of email.
Wave is actually a real-time document sharing and editing system. Imagine creating an article in a wiki and then inviting a lot of people to add to it as they chose, or you could do the same in Google Docs. Rather than creating an email thread, Wave creates a shared document. It looks a lot like an email thread in Gmail. The strength of this approach is that it does facilitate real-time communication among potentially large groups of people. The weakness of it is that it does the same, so you can easily end up with a lot of text and opinions flowing at a high rate of speed. Every time I log into Wave, I have to read through all the messages (think posts and comments in the blog format) that have been added since I was last on it. I could find only four of my friends already on Wave (and they must not be thrilled with it, since none of them responded to my Waves at them, meaning they are not logging on very often), so I have been participating in several public waves, and I have not yet gotten any experience in waving among small groups. Wave keeps the discussion arranged in an orderly, easily-understood way, even though the message volume and number of participants is high. For instance, the Software Roles in Education wave has over 145 participants. The List of Things Google Wave Will Kill wave has over 440. Most of these are talkative people with a lot of insight, and they all contribute multiple comments, so this is a lot of thinking to keep track of. Wave does a great job. However, the truly outstanding thing that Wave does is make all this happen in real time. You can actually watch the characters appear on the screen, as people type. (Some users have complained about this and seen it as a negative. They believed it made their thought processes too public. I would recommend that they draft their messages off-line, then. That is simple enough. I do it all the time in email so I don't send half-baked ideas in poorly drafted prose to people who need well thought-out ideas in carefully crafted prose featuring actionable bullet points. This is more of an issue for a work flow and writing discussion, and is neutral as far as platform.)
So, to conclude, after only a few days on Wave, here is my last post to the Is Email Better than Wave wave:
I think it is premature to attempt such a judgment. Wave is still in pre-release development, and there are insufficient users to test it fully. The basic concept of creating a shared, real-time, document among a work group is sound and will no doubt be useful, though this has been possible with wikis and Google Docs for some time. I think that as Wave is opened to more users, and as the slowness and other problems are worked out, the creative mind of the user collective will discover and develop uses that we cannot now imagine.
If you are on Wave, please connect with me. My name on it is staffordpeyton@googlewave.com.
Being a careful sort, I worked my way through LifeHacker's book on how to use Wave before I actually logged onto it. Once onto it, I could see it was completely different from what I had hoped for. I was looking for a way to integrate my online communication, which comes in via email, chat, SMS, Twitter, FB, etc., so that even though I have the ultimate email-based GTD system in place, there are a lot of messages (meaning tasks and projects) that have to happen outside of email.
Wave is actually a real-time document sharing and editing system. Imagine creating an article in a wiki and then inviting a lot of people to add to it as they chose, or you could do the same in Google Docs. Rather than creating an email thread, Wave creates a shared document. It looks a lot like an email thread in Gmail. The strength of this approach is that it does facilitate real-time communication among potentially large groups of people. The weakness of it is that it does the same, so you can easily end up with a lot of text and opinions flowing at a high rate of speed. Every time I log into Wave, I have to read through all the messages (think posts and comments in the blog format) that have been added since I was last on it. I could find only four of my friends already on Wave (and they must not be thrilled with it, since none of them responded to my Waves at them, meaning they are not logging on very often), so I have been participating in several public waves, and I have not yet gotten any experience in waving among small groups. Wave keeps the discussion arranged in an orderly, easily-understood way, even though the message volume and number of participants is high. For instance, the Software Roles in Education wave has over 145 participants. The List of Things Google Wave Will Kill wave has over 440. Most of these are talkative people with a lot of insight, and they all contribute multiple comments, so this is a lot of thinking to keep track of. Wave does a great job. However, the truly outstanding thing that Wave does is make all this happen in real time. You can actually watch the characters appear on the screen, as people type. (Some users have complained about this and seen it as a negative. They believed it made their thought processes too public. I would recommend that they draft their messages off-line, then. That is simple enough. I do it all the time in email so I don't send half-baked ideas in poorly drafted prose to people who need well thought-out ideas in carefully crafted prose featuring actionable bullet points. This is more of an issue for a work flow and writing discussion, and is neutral as far as platform.)
So, to conclude, after only a few days on Wave, here is my last post to the Is Email Better than Wave wave:
I think it is premature to attempt such a judgment. Wave is still in pre-release development, and there are insufficient users to test it fully. The basic concept of creating a shared, real-time, document among a work group is sound and will no doubt be useful, though this has been possible with wikis and Google Docs for some time. I think that as Wave is opened to more users, and as the slowness and other problems are worked out, the creative mind of the user collective will discover and develop uses that we cannot now imagine.
If you are on Wave, please connect with me. My name on it is staffordpeyton@googlewave.com.
Friday, July 31, 2009
Google Engineering Director Spells Out Vision for the Future of Digital Books - mediabistro.com: BayNewser
This is quite interesting because it goes far beyond Google's plans for out-of-copyright and OOP books. I like the idea of having the book files in the cloud, but I don't see why they have to be on Google's servers. There's no reason they couldn't reside on other servers. The main idea, though, is that readers would have permanent rights to their e-books, and that they could read their books on any hardware platform. This would solve a big problem and prevent monopolistic companies from dominating the e-book market. The other good idea is that with the spread of the Espresso Book Machine and similar instant book printing devices, this model would support rather than undermine independent bookstores.
Two big questions about e-book licensing remain unanswered: can these books be re-sold and can they be bequeathed as part of an estate? I think the answer for e-books will always be negative because publishers will not want to lose control of the content or to allow a used e-book market to open up.
Tuesday, February 17, 2009
Google & the Future of Books - The New York Review of Books
Google & the Future of Books - The New York Review of Books
Excellent article by Robert Darnton, head of libraries at Harvard, explaining the likely outcome of the Google Book Search settlement. Thanks for Jim Scheppke for pointing it out.
Excellent article by Robert Darnton, head of libraries at Harvard, explaining the likely outcome of the Google Book Search settlement. Thanks for Jim Scheppke for pointing it out.
Monday, January 5, 2009
For the Blind, Technology Does What a Guide Dog Can’t - NYTimes.com
For the Blind, Technology Does What a Guide Dog Can’t - NYTimes.com
Interesting article on TV Raman, Google's expert on assistive technology, and some of his adaptations for blind users.
Interesting article on TV Raman, Google's expert on assistive technology, and some of his adaptations for blind users.
Subscribe to:
Posts (Atom)
Posts
