Two Reasons I Do Not Like Google Apps

Today I was trying to create a halfway decent looking and recent resume using a previous one I had developed as a starting point.  It was made with the Office Word 2010 beta so I decided to uploading it to see how well Google Docs works importing this pseudo-XML.  This is what it was supposed to look like (well, there was no box around my email).

Side note:  I am not a graphic artist and I don't like putting much effort into such things so yes, it is Spartan and possibly ugly.  Sorry if I offended your tastes.

Compare that with what Google imported:



You'll probably note that it's pretty decent but has some obvious issues.  Probably most obviously is the blue background image I had been using which cannot be placed behind text in Docs.  Actually that was my biggest frustration.  It wasn't just a problem with the import.  When I tried to move the image down just a little to see if I could fenagle it into working, it jumped down and displayed the full image size.

Check this:

You'll notice I've made a few other minor changes (no my name won't stay popped eye blood vessel red(tm) ) but my stupid image can't even be moved partially offscreen!  Clearly the engine is capable of supporting the function (as seen above) but it's not a feature of the editor.  WTF?











Now having read all this you might think I'm just a teenage h8r (that's supposed to be read "hater" by the way [btw]).  Not true!  I was impressed by Docs' quick response, import ability (it did keep the right formatting), Mac keyboard shortcut support, and focus.

This is what I really liked about the service.  It was an excellent WYSIWYG editor.  No, it was an incredible WYSIWYG editor.  Try it yourself.  Type in some text with complicated formatting and then insert an image.  Your options for how to insert it might be limited but within those it keeps the formatting and placement of all your data in relation to the whatever piece is being modified.

Exhibit 1:

Exhibit 2:

Clearly Google has made an effort to create a very user friendly editor.

Side note:  In switching my mom to Win7 I made her sacrifice Office 2003 and without anything to replace it.  Eventually I was forced to install OpenOffice.  Within minutes she had decided that she hated OpenOffice and would probably never use it again (until I told her to).  [Blame auto-crap.]  She was ... relieved when I showed her Google Docs.

It's an admirable goal and makes a hell of a lot more sense than any other editor I've seen.  I like it.  Something I don't think I've said in months (about anything, even in real life!).  It's nice and I never knew I could have something this nice.

Now there are still some massive problems to work out before it should be "launched."  That's right, the page might not say it but this is a beta.

Remember when I said it was the most awesomest WYSIWYG editor everzzzzz?  Wellllll about that ...

This is what it looks like when you tell it to print.  Yes, really.

Work it out Google!  You have a potentially stupendous product on your hands with some glaring issues but all that really means is they have their work cut out for them.  To it, Google!

Some interesting reading tonight.  Well, if you're into corporate ineptitude that is.  See, I just started some intensive readings on the Kin failure and I have come to one conclusion:  heads must roll.

See, to me, a head must roll when a person presents more risk to the company than he or she is worth.  A noted example of a head already rolled:  Robbie Bach.  Head of Entertainment and Devices division for several years now he recently retired.  According to his Wikipedia page (and confirmed by his MS bio page) "He led the division that is responsible for the Xbox, Xbox 360, Zune, Windows Games, Windows Mobile and the Microsoft TV platform."


Now, think about that.  The one possibly reasonably "successful" product still cost the company billions of dollars not just to develop but in damage control from extremely unreliable hardware (we have 12 360's where I work and 5 are broken and out of warranty).  Nothing else has matched its commercial success but I don't believe anyone since Kenneth Lay has earned so much money losing money (excluding banks).


But he's gone!  What does it matter now?
Well unfortunately not every poor decision can be laid at his feet (I actually might not blame the Xbox problem on him, I just don't have the information necessary for that choice).  I have heard several other major names mentioned, mostly from the Danger group now leaving or just departed Microsoft.  The list I have seen includes but is not limited to:


Robbie Bach
J Allard
Matt Bencke
Roz Ho


Let me take a moment to especially single out that last one.  Roz Ho has been mentioned over and over again for failure in various capacities.  I have heard that the Danger team was lied to about their role post-acquisition, that Roz and Matt were responsible for deciding to acquire Danger and start the z(une)Phone project.  So just to be clear, a massively expensive team of highly talented and motivated developers (Danger) were bought solely to speed development of a mish-mash of a failing music player and a failing phone in an attempt to out-iPhone the iPhone.  All this was done just before Windows Phone 7 work commenced using a totally different, more capable base.  Roz was responsible.


As evidence of her incompetence as a leader, I'll let poster WilliamTruthTeller of the Ars Technica forums give you his opinion:
"Roz Ho was in charge of the entire PMX/Pink effort. This was her very first (and assume last) mobile effort. Previously she was in charge of the Mac office efforts at Microsoft. I have never met a less competent leader. She was shallow and completely self absorbed and will find any excuse to talk about herself. She made it clear to the entire team that she has a lot of money and loved to talk about it. She has houses in Redmond, the Los Altos Hills, a condo at Squaw Valley and an apartment in Chicago. She has more than 4 cars one of which is an Audi A10. We only knew these details because she was always talking about them. Nobody cared but she couldn't help it. The ultimate expression of her clueless pomposity was than during the heat of the development battle, when the project was struggling mightily with technical and personnel problems, she took three weeks off to hike to the top of mount Kilimanjaro . . . Just so you understand how terrible these two were in their roles as leaders, both Roz and Matt were assigned executive coaches to review their communications because they didn't have the internal ability to detect when they might destroy morale through their clueless statements."
So morale was down.  Roz was responsible.


Management didn't know how to handle technical issues.  This is evident in the almost vaporware status of Windows Mobile Phone 7 and carries over also to Pink/KIN.  Another post:
"In the middle of this mission to save WM7, Roz shows up with some of the PMX folks and says they are going to need his support. They are using a different chip set and will need changes made in the core to support it. PMX not only needed changes in the core, but also needed WM personnel to act as engineering support to PMX. And Terry M. correctly said "No and hell no." . . . MX made its own mess and would have to pull itself out."
Roz was responsible.


Noticing a pattern here?  There are plenty of other examples of Roz and also others making gross managerial mistakes but in my view, none tops this.  The title reads, "Microsoft's Pink/Danger backup problem blamed on Roz Ho."  Trimming the fat, the article says that she was told by the SAN provider that there should not be a problem doing an in-place upgrade on existing equipment (realize that this is expensive equipment and takes 6 days to back up because of the volume).  She decided two days into the backup that money could be saved by not backing up.  Since there was only room for one backup and the last one had been deleted to make room for the one in progress well...  headlines were made.  The biggest mobile data loss in history and I can tell you from experience that the service hasn't been the same since (Calendar and email syncing problems existed for me as a new customer in January.  I kept the phone for five days.).


So probably every manager in the department should be fired.  But that's unlikely.  Seeing someone as visible and with as deep a history at Microsoft as Roz leaving would be a good start.