Hmmm, this is interesting, because when I was in college (early 2000s), most of Apple's docs were littered with "description forthcoming" EVERYWHERE. The only w

Hmmm, this is interesting, because when I was in college (early 2000s), most of Apple's docs were littered with "description forthcoming" EVERYWHERE. The only way you could possibly understand the proper behavior was to use a framework (PowerPlant), or spend thousands to go to WWDC and ask engineers. But Apple wanted everyone to adopt Cocoa and invested heavily in making it as appealing as possible. What probably happened, they hired some bright well managed senior copywriters who ran a tight ship under the Steve Jobs era and cleaned up the mess. Best practices were defined and as best as Apple could, they explained how to take advantage of OS X and iOS. I mean, important nuggets would still sometimes fall through the cracks, but for the 80% case, you had really good documentation. At that time, Apple was known for its Human Interface Guideline textbook with full color check-lists of Dos and Don'ts that really influenced the spread of skewmorphism around to other platforms. What probably happened is they left, and if the writers had not completely burned out, Google and Facebook do pay way better and offer much better work/life balance. So Apple is probably left with mostly new grads who don't have families and so when an exec asks them to move the documentation to iCloud, it's probably just been one mismanaged cluster fuck after another. I suspect they'll eventually finish the migration and it'll be back to world class again.