Organ Banked
In response to my roundup about Apple’s software quality, a former Apple CoreOS person writes:
A lot of us felt we were being “organ banked”, and late in Lion, on the iDevice release cycle, we were pulled away from desktop work in order to do iPhone and iPad work, which was on a 3 month release cycle, instead of alternating desktop with non-desktop, which we had formerly done on a 6 months on/6 months off cycle (release one in fall/release the other in the spring).
The desktop vastly suffered because of this, and we felt that Lion and later were more or less “phone it in” releases for the desktop.
The comments from Apple insiders underscore that there are many factors that affect software quality. It is not simply a matter of dropping the yearly schedule or of deciding to do “another Snow Leopard.” The development schedule and cycles matter. It also matters who the engineers and managers are, how they are treated, whether they are shuffled between projects, etc.
There was a lot of resentment because when the initial iPhone came out, almost no one on the second floor of IL2 was allowed to look at the internal SDKs; even after the SDKs were finally released (a lot of Apple engineers by that point were on the “iPhone Dev Team”, and compiling their own apps for jailbroken phones, providing compiler and assembler fixed, and so on).
Then we had to wait 6 months after they started external classes before we were allowed on the platform, or in the classes. We all suspected that that was because there was incredible demand for iPhone programmers, and we’d get hired away from working on boring old crap like Finder and Mail and AddressBook, because Apple couldn’t hire people willing to work on boring crap any more.
This reminds me of three things:
- Guy English’s 2012 warning: “Ultimately, the retention of talent will be Apple’s Achilles’ heel.”
- The lengths that Apple went to to prevent other companies from hiring its employees (and former employees).
- The iPhone SDK NDA. Patents have been floated as one possible explanation, but the NDA is still somewhat of a mystery. Obviously, it did nothing to prevent competitors like Google and Microsoft from learning about how the iPhone worked. They could simply register as third-developers and get access to the SDK. (Apple wanted them to write apps, after all.) There is one group that presumably could not do that, though: Apple’s own employees. Perhaps one purpose of the NDA was to act as a sort of Great Firewall of China, blocking Apple’s own employees from accessing information that would make them more difficult for the company to retain.
Update (2019-06-03): Dave DeLong:
I’ve been hearing of multiple @apple engineers who are being forced to leave the company because of the “no remote” policies. They have DECADES of combined experience who love the company and want to stay.
It’s pretty upsetting to see Apple hemorrhage talent like this
2 Comments RSS · Twitter
"because Apple couldn’t hire people willing to work on boring crap any more."
Which is a completely dumb way of thinking. There are plenty of people who would enjoy fixing the zillion issues in these system applications.
