Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!

 



Forgot your password?
typodupeerror
×
Google Businesses The Internet

Pleasing Google's Tech-Savvy Staff 142

An anonymous reader writes "Douglas Merrill, Google Inc.'s chief information officer, is charged with answering that question. His job is to give Google workers the technology they need, and to keep them safe — without imposing too many restrictions on how they do their job. So the 37-year-old has taken an unorthodox approach. Unlike many IT departments that try to control the technology their workers use, Mr. Merrill's group lets Google employees download software on their own, choose between several types of computers and operating systems, and use internal software built by the company's engineers. Lately, he has also spent time evangelizing to outside clients about Google's own enterprise-software products — such as Google Apps, an enterprise version of Google's Web-based services including e-mail, word processing and a calendar."
This discussion has been archived. No new comments can be posted.

Pleasing Google's Tech-Savvy Staff

Comments Filter:
  • Re:NO TFA (Score:2, Informative)

    by orclevegam ( 940336 ) on Wednesday March 19, 2008 @10:58AM (#22795546) Journal
    Reload the page, it worked for me. Looks like their server is having a minor case of slashdotting.
  • The question is... (Score:2, Informative)

    by adpsimpson ( 956630 ) on Wednesday March 19, 2008 @11:03AM (#22795614)

    From the article:

    "How do you run the information-technology department at a company whose employees are considered among the world's most tech-savvy?"
  • by ccguy ( 1116865 ) * on Wednesday March 19, 2008 @11:24AM (#22795870) Homepage

    So who writes these 'automated tools' and who checks those?
    Most likely they use those tools to check themselves, pretty much as you compile (most of) a compiler with itself, debug a debugger, and so on.

    If you are interested in how these recursive tools work, check valgrind [valgrind.org]'s documentation (interesting because it relates a bit how some design decisions were made so that valgrind could be used on itself) for example.
  • by mc900ftjesus ( 671151 ) on Wednesday March 19, 2008 @11:38AM (#22796060)
    Does IT make the company money? No, not a dime, they're a money sink-hole like electricity and phones. They don't call the shots just like the maintenance man doesn't call the shots. IT departments need to be enablers. When IT crosses the line from preventing you from installing tons of crap on your desktop to killing the rollout of a platform that generates revenue, someone in management should have been fired on the spot, no questions asked. IT should never dictate a product, only internal policy.
  • by dangerz ( 540904 ) <stuff@NoSPAm.tildastudios.net> on Wednesday March 19, 2008 @11:56AM (#22796292) Homepage
    This app started in PHP before I was here. When I came in, I rewrote it in PHP to make it more efficient and strip out some of the fat. There were emails with IT on it and they didn't seem to care. It wasn't until the app got popular and used that it became an issue.

    My management did their best to fight it, but IT has a strong pull here I guess.
  • Comment removed (Score:4, Informative)

    by account_deleted ( 4530225 ) on Wednesday March 19, 2008 @12:01PM (#22796346)
    Comment removed based on user account deletion
  • Re:Nice approach (Score:3, Informative)

    by SanityInAnarchy ( 655584 ) <ninja@slaphack.com> on Thursday March 20, 2008 @12:54AM (#22803682) Journal

    Your logic is faulty.

    Show me how.

    The first hacker to take down their network, either internal or external facing, would be infamous.

    And traditional viruses/spyware won't do that.

    The trouble is, modern OSes are reasonably secure at this point, and you can bet the external-facing IPs are going to be locked down. Same with internal services -- some random developer's desktop might be open, but the service is going to be secure. So what you're talking about is someone actively making a "hacking" attempt at something that, to my mind, looks pretty much impenetrable.

    The only other option is something more insidious -- set up a website which exploits some browser flaw, then hope someone at Google sees it. Or sit around a wifi hotspot, praying that someone logs on with a laptop that's vulnerable, infect it, set it to phone home, then pray it is actually able to phone home, and that Google doesn't take a peek at exactly where it's phoning home to.

    And a successful variation of this is still just going to give you the one insecure machine. It's not going to give you the entire network. It's probably got less of a chance of doing that than if they were extremely anal-retentive in their security policy (and refused local-admin rights, etc), because it's going to be a heterogenious network.

    But then, you did just provide the perfect counterargument: The first hacker to take down their network, either internal or external facing, would be infamous. Therefore, people are trying. It's not working. Therefore, whatever Google is doing for security is working.

  • Re:Nice approach (Score:2, Informative)

    by V for Vendetta ( 1204898 ) on Thursday March 20, 2008 @01:44PM (#22808826)

    Have software clickwrap licences even been tested in court yet?

    Yes. At least in Germany. Here, you, the purchaser, need to able to reed the EULA/ToS before even buying the software.

Organic chemistry is the chemistry of carbon compounds. Biochemistry is the study of carbon compounds that crawl. -- Mike Adams

Working...