Interesting... I was going to make an observation that's partially borrowed from one of my co-workers. We both agreed that this big new Apple campus could potentially be the shot in the arm that Apple needs to remain competitive.
A lot of people seem to be viewing it negatively, as the opposite of what the company used to be about, etc.
But from our perspective? One of Apple's ongoing struggles seems to be insufficient manpower to keep working on multiple product lines at one time. Whenever the pressure is on to improve the iPhone, for example? It seems they're borrowing staff from the Mac OS X side to help get it completed on time. And how many good software applications have they just given up on, presumably because they had "more important things" to focus on? (EG. Aperture or products like "Color" and "Soundtrack Pro" that used to be bundled with Final Cut Pro Studio.)
I've always had the impression that Apple was understaffed, but perhaps they found that preferable to getting bloated, with too many hires who weren't really contributing enough? I think with the change in focus from being "Apple Computer" to "Apple (the electronic gadget maker and music and video sales people)" -- there's a need for a much bigger base of employees to get all of it done.
This campus gives some hope that can happen, and maybe THEN we'll see some faster innovation.
Actually, that is a wide misconception. Not getting into specifics, but towards 2008 Cook began making the decisions as Jobs focused on the iPad release that truly launched the iPhone (long story on that one as well). As Jobs' health worsened he focused on his family and the iPad launch.
Jobs' other project in limbo since 1984 finally broke ground. The Spanish Colonial Revival 'Jackling house' designed by architect George Washington Smith in the early 1900s for copper magnate Daniel Jackling was finally approved for demolition by the courts in 2010 after Jobs bought in 1984 and fought preservation societies/groups and city council(s). Plans for the new structure were finalized years ago and Jobs was already retired behind the scenes. He knew his time was short and wanted to build his designed home almost 30 years in the making (the design was quite modest in size and aesthetics with some very innovative technology that Jobs and Ive hoped to showcase at some point). Sadly, the lot is empty as the mansion was demolished and Jobs passed away before it was built.
The Apple Campus was 75% Ive. Jobs entertained the idea and fought for its approval, but behind the scenes he lamented its ostentatiousness as it evolved into something very different than he imagined. However, he felt the need to let Cook make the decisions during his transition and decided to "let go" and enjoy his remaining time. He still worked from time to time, but the rumors that he worked up until his death weren't true.
[doublepost=1477959560][/doublepost]There was a time when I would have agreed 100% with this. And for the record? I still think telecommuting is the smarter way for companies to approach hiring for quite a few people in the workforce.
But if you want to know why Apple wouldn't just settle for remote software developers? Take a look at the garbage Microsoft has been cranking out lately with the largely Indian workforce. Sure, you can find a bunch of warm bodies who know how to write code, but without making them part of your corporate culture and having the ability to randomly chit-chat, overhear random conversations in the hall or at the water cooler, etc. -- they're at a real disadvantage grasping the whole concept of what you're shooting for as the resulting application.
I don't code myself, but there was a time when I did. And one thing I learned is that you can certainly be a lone developer, working on your "baby" -- and put out a top-notch product. That's because your heart and soul are poured into it and you have the vision of what it's supposed to be. You coded everything in it so you can work on pretty much anything in it. But these commercial projects are team efforts. A bunch of "lone wolves" just coding the little portion they're instructed to code really don't have the vision (or even the pride) in the end product as a whole.
I don't disagree that Apple is environmentally friendly, but insisting that new employees relocate is about as environmentally unfriendly as you can get. There's no technical reason why programmers can't work remotely.