Post by Mark T. Tomczak

199d

@pikesley I think that one's not actually technically incorrect; it's a symlink to the README.rst file one directory up. In this case, it's GitHub that's letting you down by not chasing the symlink when you click that link instead of showing you the raw contents; if you were looking at the source in a local filesystem, the right thing should happen.

(... of course, I'd probably have done that not by trusting symlinks, but by putting a .rst file here that just says "See the README file [here] for more information").

Edited 199d ago

1 0 0 View Post & Replies See Original

199d

@mark as you might imagine, I'm in no mood right now to give them the benefit of the doubt. I have long-abandoned half-finished nonsense on Github that works better than this

1 0 0 View Post & Replies See Original

199d

@pikesley I hear ya and I wish you luck. When I was there, I had real strong feedback for the docs team on how OAuth was doc'd. Something to the effect of "You gave me three different technical explanations in three different sections of the code maintained by three different teams... and no working examples."

I got the sense that the open-loop at Google is nobody was tasked with plucking a naive user off the street, sitting them down, and paying them to go through the docs and try to do something.

(... FWIW if there's anything I can help with LMK. My knowledge is rusty and ancient and may be out of date, but I still have some of the old patterns jangling around in my brain and I might be able to help clarify WTF Google was thinking in these APIs. Cloud used to be the team I was in).

Edited 199d ago

0 0 0 View Post & Replies See Original