3 ms·
One doesn't need to write perfect documentation to point out bad documentation. That said, I was hoping for more concrete examples.
by epalm 7y ago
One doesn't need to write perfect documentation to point out bad documentation. That said, I was hoping for more concrete examples.
- macinjosh 7y ago> One doesn't need to write perfect documentation to point out bad documentation. Agreed. Calling something 'garbage' and providing no concrete examples isn't really constructive feedback. It is just name calling.
- jasonlotito 7y agoNot the OP, but I'd provide some examples if there were examples to provide. Unfortunately, their documentation is severely lacking in the area I've worked with recently (Apple Sign In on the server end). Basically, it doesn't exist. I can't point to a specific example other than to say it doesn't exist. And this should be concerning. If Apple wants people to use Apple Sign In, they should do more than mandate its use. They should make it easy to implement, or, at the very least, provide clear documentation. Instead, I've had to rely on other documentation outside of Apple that all start by sharing their disappointment with Apple's documentation on this subject, and then try to decipher what Apple is doing.
- chriskrycho 7y agoThis comment was one of the ones that led me to update the title of the post. My intent: "Having this much missing is garbage." How people took it: "What exists is bad." Thus, the rewording to "Missing."