{"id":2104,"date":"2007-06-27T11:40:46","date_gmt":"2007-06-27T16:40:46","guid":{"rendered":"http:\/\/blog.librarysupportstaff.org\/?p=356"},"modified":"2007-06-27T11:40:46","modified_gmt":"2007-06-27T16:40:46","slug":"working-at-google-vs-working-at-microsoft","status":"publish","type":"post","link":"https:\/\/www.libology.com\/blog\/2007\/06\/27\/working-at-google-vs-working-at-microsoft.html","title":{"rendered":"Working at Google vs. Working at Microsoft"},"content":{"rendered":"

This isn’t directly related to libraries, and even the indirect aspect only applies to larger libraries, or libraries within larger institutions, but I thought there were some points of interest in this blog post from an anti-Google blog<\/a>.<\/p>\n

Of special interest to me is how Google handles their IT issues (near the end of the post). They have a local IT person (one per floor, it seems) who handles initial troubleshooting, updating and changing equipment, and other tech-related issues. This looks like a very flexible and quick system to get people what they need to keep working effectively. I have lost count how many times something like this would have been beneficial for a workplace.<\/p>\n

Some of the gripes (office space, management structure, insurance) could be a reflection of what that particular employee values in their work experience. They could also reflect growing pains on Google’s part, so I leave it to the reader to decide where they would prefer to work, or at least which of these ideas could be applied to your library.<\/p>\n

found on Search Engine Land<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

This isn’t directly related to libraries, and even the indirect aspect only applies to larger libraries, or libraries within larger institutions, but I thought there were some points of interest in this blog post from an anti-Google blog. Of special … Continue reading →<\/span><\/a><\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":false,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2}},"categories":[2920,2934],"tags":[5350,3121,3016],"class_list":["post-2104","post","type-post","status-publish","format-standard","hentry","category-blogs","category-google","tag-google","tag-microsoft","tag-search-engine"],"jetpack_publicize_connections":[],"jetpack_featured_media_url":"","jetpack_shortlink":"https:\/\/wp.me\/pSU5g-xW","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/www.libology.com\/blog\/wp-json\/wp\/v2\/posts\/2104","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.libology.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.libology.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.libology.com\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.libology.com\/blog\/wp-json\/wp\/v2\/comments?post=2104"}],"version-history":[{"count":0,"href":"https:\/\/www.libology.com\/blog\/wp-json\/wp\/v2\/posts\/2104\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.libology.com\/blog\/wp-json\/wp\/v2\/media?parent=2104"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.libology.com\/blog\/wp-json\/wp\/v2\/categories?post=2104"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.libology.com\/blog\/wp-json\/wp\/v2\/tags?post=2104"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}