Comments on: Google Employees’ Guiding Principles at Work http://blog.blogsthatfollow.com/2008/04/google-guiding-principles/ Official Blog of "Do Follow" Blog Directory. Blurbs on SEO, Technology, Business, Marketing, and more... Wed, 16 Jun 2010 21:50:29 +0000 hourly 1 http://wordpress.org/?v=3.0 By: Simon - presentation skills training UK http://blog.blogsthatfollow.com/2008/04/google-guiding-principles/comment-page-1/#comment-277 Simon - presentation skills training UK Fri, 30 May 2008 14:58:11 +0000 http://blog.blogsthatfollow.com/?p=84#comment-277 I take your point but I don't think that's what this guideline is getting at at all. I interpreted it as meaning that people weren't to get too hung up on the "way things were" or the "way things were done". It's not about "we can change it if it's wrong" it's about "let's change it if we can make it better". S I take your point but I don’t think that’s what this guideline is getting at at all. I interpreted it as meaning that people weren’t to get too hung up on the “way things were” or the “way things were done”. It’s not about “we can change it if it’s wrong” it’s about “let’s change it if we can make it better”.

S

]]> By: lift chairs http://blog.blogsthatfollow.com/2008/04/google-guiding-principles/comment-page-1/#comment-220 lift chairs Fri, 16 May 2008 20:12:35 +0000 http://blog.blogsthatfollow.com/?p=84#comment-220 I have always like the Google atmosphere, but I don't know if I agree with #3. When you consider all the credit card and other personal information that is housed at Google this 'rule' comes across as sort of alarming. From a security standpoint if you just write code and figure you'll fix it as it breaks, you are doing a great disservice to everyone who uses your code. Of course this isn't an official Google document, but it seems to represent at least some of their employees. I have always like the Google atmosphere, but I don’t know if I agree with #3. When you consider all the credit card and other personal information that is housed at Google this ‘rule’ comes across as sort of alarming. From a security standpoint if you just write code and figure you’ll fix it as it breaks, you are doing a great disservice to everyone who uses your code. Of course this isn’t an official Google document, but it seems to represent at least some of their employees.

]]>