4 ms·
Ken is a friend and colleague. I worked with for years on the Go team, from the early days. But ken was at Google a long time before the Go project started. (T
by enneff 6y ago
Ken is a friend and colleague. I worked with for years on the Go team, from the early days.
But ken was at Google a long time before the Go project started. (The Go project was not developed in Google's monorepo and was not subject to Google's readabiliy process, as is the case for many Google projects.) What ken was referring to was indeed the C++ Readability process (which doesn't stop anyone committing code, just requires a review from a person with the 'readability' certification before committing; as mentioned upthread). I know this from talking to him about it, specifically.
I can't offer you any more proof other than the fact that I was a witness. If you don't believe that, then I'm sorry? Not sure what else to tell you.
FWIW your conduct in this thread is extremely obnoxious. I'm sure you'll find a way to debate that, too, but please consider that I have no vested interest in telling you this other than hoping you might better learn how your conduct is perceived by others.
- acqq 6y ago> I know this from talking to him about it, specifically. Perfect! So what's the exact story, then, finally? 1) Was the quote from him completely invented? 2) Was he allowed to check in or not? Did he need the test to check in at that moment to which the quote refers? (I don't care about the moment when it was published). 3) And even more specifically: were there ever the times where he was in Google but when he not able to check in the code lacking some Google-prescribed "test"? Just "yes", "no" or "I don't know" there, please. Also (just for my curiosity): 4) How long that period lasted? Then you can elaborate where I was wrong by searching thorough what I've written -- I've specifically quoted the article and talked about his C background and involvement in a new language, never claimed anything about his C++ code and a "certification." I have an impression that your perception of what I've written and that, what I actually have written don't match.