writes: Business Insider and All Things D are reporting that Yahoo CEO Marissa Mayer's decision to ban telecommuting was as data-driven as you'd expect out of the former Google exec. After spending months frustrated at how empty Yahoo parking lots were, Mayer consulted Yahoo's VPN logs to see if remote employees were checking in enough. Despite all the outrage and flak she's getting from those outside the company for the move, some ex-employees are praising the decision, citing abuse, slacking off, and general "unavailability" of folks working from home.Link to Original Source
writes: I work for a traditional "old school" software company that is trying to move into web services, now competing with smaller, nimbler "Web 2.0" companies. Unfortunately our release process is still stuck in the '90s. Paperwork and forms, sign-off meetings, and documentation approvals make it impossible to do even minor deployments to production faster than once a month. Major releases go out a couple of times a year. I've heard from colleagues in Bay Area companies who release weekly or daily (or even multiple times a day), allowing them to adapt quickly. Slashdotters, how often do you push software changes into production, and what best practices allow you to maintain that deployment rate without chaos?