9 ms·
Am I the only one thinking that this contract was probably bound under an NDA, and that making such a post is generally bad practice leaving employment/a contra
by davidjgraph 14y ago
Am I the only one thinking that this contract was probably bound under an NDA, and that making such a post is generally bad practice leaving employment/a contract (regardless of whether there's an NDA).
I know nothing ultra-secret is given away, but if I were looking for a contractor, I'd be concerned that such a person might perform a post-mortem on my company after leaving as well.
- eliben 14y agoI'll second this. I think such a post from a contractor is inappropriate, unless he cleared it with some Google authority, which I doubt he has.
- j_baker 14y agoWhat confidential information did he reveal?
- eliben 14y agoI don't know. But reading his post it's obvious he discusses a lot of details of the internal development methodology in Google which seems like something you should ask for approval to publish.
- j_baker 14y agoYou don't know that anything he said is confidential. You don't know that he didn't get approval for this, which you say he "should" do clearly without knowing anything about Google's policies. I'm also assuming you don't know what his NDA specifies. How can I construe this to not have you reaching a premature conclusion with too little info?
- eliben 14y agoI did say "... unless he cleared it with some Google authority, which I doubt he has." So what are you specifically objecting? My saying that I doubt he cleared it with Google? I'm entitled to my doubts, thank you :-)
- j_baker 14y agoIt strikes me as being officious to judge a person's actions as "inappropriate" without having the proper context (what their NDA says, what Google considers confidential, etc).
- pnathan 14y agoHonestly, I've heard the majority of it before, and I have never been a Google employee. I have, however, listened to some of their talks on the internal workflows and processes that they've presented and posted on youtube. I think the only things I didn't hear before were some of the specific toolnames. edit: http://google-engtools.blogspot.com/ http://google-engtools.blogspot.com/ here's their engineering tools blog. http://www.youtube.com/watch?v=2qv3fcXW1mg http://www.youtube.com/watch?v=2qv3fcXW1mg and a talk http://www.youtube.com/watch?v=b52aXZ2yi08 http://www.youtube.com/watch?v=b52aXZ2yi08 and another talk Really cool stuff.
- beering 14y agoFor those wondering, there's nothing in his post that couldn't be found with some Googling. There's info in here that probably crosses the line of what shouldn't be made public, but at least he didn't go to the extent of using the internal codenames.
- angersock 14y agoMaybe it'd be good for your company to shine in a post-mortem when talking about development practices. Secrecy is stupid for these things.
- United857 14y agoAt the very least, most of the tools mentioned (gyp, KIF, etc) are used in other open source projects like Chromium and are not Google internal.