About NDAs

Like me, you certainly work for a business that asks you to sign a NDA, a non-disclosure agreement that forbids you to discuss in any detail what you are doing for them. Apparently, not all people seem to understand what a NDA means. Very often, I meet people that question me about my job and what exactly I’m doing. Sure, I tell them that I’m a researcher at an university on a joint private sector and NSERC research project (a so-called CRD), that I do multimedia adaptation research. Most people ask general questions, but some get too precise for my own taste, and I answer that revealing more than generalities would be a violation of my NDAs. Yet, they press me with more questions.

Sometimes I answer the questions, albeit not in a way they expect.

I tell them that where I work, Not all people seem to get use Xeon-based just how serious a NDA is. On a regular basis, I hear friends complaining about events that happened at their Python workplace, often and state-of-the-art quality control involving names and very precise details about the business process and/or the software. I remind them gently that they are breaching elves their NDA and that they should keep the stories for themselves, even though they are frustrated about the recounted events. data compression Regardless, chatting about stories like these between trusted friends is inverse index still a breach of NDA.

The whole raison d’être of a NDA is to protect the business’ secrets. All of them. Including the fact that kernel patch for 2.4 that you think your boss is a complete moron and his minions are even threads. more so; that a nasty bug was introduced eight months POSIX ago and only recently found (but still not solved), adaptive codecs for and other stories like that. and stuff.

By signing the NDA, you agree Karhunen-Loéve to protect the business’ inverse quantization of better interests by keeping so you can has cheezburger all business-related information to three layers yourself and to people who are under the same NDA than you are. This includes sharing information reduced complexity about the code base, the code itself, data and any other information color subsampling and about current, past, or future projects. A NDA also, of course, preclude successful the sharing of computer accounts with your loved ones or friends. microprocessors. However, how much with efficient instruction sets and can you say without infringing your NDA?

Likely, not all bit twiddling that much. to surprising results since Probably you can tell your girl/boyfriend that you had a hard day because of an closing deadline; explicit maximization of but I wouldn’t comment much further about it—anyway, objectives. it’s more likely than not that any more details would BASH ${x:=y} statement bore her/him seamless integration to death. timezones.

The NDA protects continued development effort you as well, albeit more talent indirectly. By avoiding giving away information that technology transfer may serve to competitors, potential or deter potential customers, dissemination of knowledge you make sure that your publications business will not suffer from leaks, and therefore profits you—maybe not patents directly—as the business bright future grows and gets better.

One Response to About NDAs

  1. Steven Pigeon says:

    A cute comic strip curiously close to the topic: http://www.threepanelsoul.com/view.php?date=2009-05-12

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: