Hacker News new | past | comments | ask | show | jobs | submit login

I 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.



You 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?


I 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 :-)


It 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).


Honestly, 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/ here's their engineering tools blog.

http://www.youtube.com/watch?v=2qv3fcXW1mg and a talk

http://www.youtube.com/watch?v=b52aXZ2yi08 and another talk

Really cool stuff.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: