Hi Danny, Thanks for your advice!
But please don't take it the wrong way. IP protection policy doesn't mean a company does not trust their employees! Or otherwise, why there is something called NDA, right? Why not simply employ the ones you trust? It doesn't matter if one joins a company or work in a university, they will be asked to sign a paper claiming something like they won't steal things. At least European and Asian universities and companies generally do this. On one hand, IP protection policies is a very common mechanism in an organization and it definitely doesn't mean a company doesn't trust its employees; on the other hand, when a company grows fast, how can somebody promise that you know every applicant so well that you are so sure that each of them can be trusted equally even when people are from different countries with different backgrounds? Anyway, we are a great team working together and of course we trust each other. The IP protection techniques we were looking for was meant for new employees whom we don't know that well yet. AND, I wanna thank everyone here replying my questions! I do get what I wanted to know on the first place! Thus, I'm gonna move on to the dev work and close this thread. Thanks again! Regards, Sean PS: Because Danny has some opinions that sound similar to the ones proposed by Michael. Therefore, I also wanna finish this thread by rewriting some of my opinions wrt. Michael's reply. I don't really remember what I wrote for the first time. I'll just quickly recap some of my previous thougts concerning Michael's opinions. ============= Hi Michael, Thanks very much! You are right. It's not a good idea to be suspicious as an employer. But try to protect IP != suspicious. Plus, I'm not trying to say we don't want anyone to get the entire code base. The core team obviously have the authorization to touch everything and we only want to get some kind of control over our new employees to reduce potential risks. Apparently, IP protection is not something new. Big companies do such things all the time, not just by asking their employees to sign up some NDA. And we shouldn't say that those big companies are suspicious about their employees. It's just one kind of risk control policy. Further more, I believe code leaks and IP thieves are also not brand new concepts. And there is one more thing, working environments and attitudes are sometimes different in different countries. People sometimes simply couldn't really understand such situations thoroughly if they were not growing up in that environment, a little bit like different religions. In short, now I get some rough ideas about web developers' opinions on IP protection and I'll try to fit into the community. Therefore, I think I will try to be more open. FYI, I've been working on system software and robotics systems which are usually developed in C/C++ wrt. computer programming. We also design mechanical and electronic systems. For our projects, we usually use differently techniques for IP protection and our team work well. ....... ============= On Feb 27, 4:54 am, Danny Burkes <[email protected]> wrote: > If you don't trust your own developers, you have bigger problems than > any obfuscation or compartmentalization scheme can solve. > > Find developers that you consider your trusted colleagues and build your > product with them. > > - D > > -- > Posted viahttp://www.ruby-forum.com/. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
