The final decision on this is probably above the OP's pay grade, but consider putting employees on the "Bring your Own Laptop" plan. One of your biggest expenses at a company this size (unless you have very expensive vertical market software) is desktop hardware. Company-owned machines take a lot of hard use, and somehow people's own property lasts longer.

You need to be able to recover from a crash anyway, so why write both: infrequently used but critical crash recovery and frequently used, but not always run clean shutdown? Just crash. Crash-only software: More than meets the eye

Before Google, "search engine optimization" was basically choosing a good page title, then stuffing the page with keywords.

Then Google came along, and PageRank saved the web from crap keyword-stuffed pages. All of a sudden, placement was based on whether or not a page could attract inbound links. Life was good.

Now, Google is tracking click-throughs using JavaScript, resulting in putting less and less weight on PageRank, and more and more weight on...keyword stuffing. Yes, you're using Google Math to weed out the auto-generated crap and duplicate pages, but keyword stuffing is back in a big way. (If I were wrong about this, Demand Media and other "content farms" of crap pages would not exist.)

I'm not worried about Google making us "stoopid" but are we making Google stoopid?

I just started as an editor at No Starch Press. The company is already set up for LaTeX and Subversion, and we're introducing git.