3 ms·
That's so generic - "basic CRUD(website)". It's ridiculous. You're a UI developer, of course you're going to design a UI for CRUD functionality in the next five
by mjhea0 12y ago
That's so generic - "basic CRUD(website)". It's ridiculous. You're a UI developer, of course you're going to design a UI for CRUD functionality in the next five years.
My problem with NDAs is that even if the company decides to pivot and abandon the "idea" altogether, you are still bound by the NDA for that time frame. It restricts creativity. Shows a lack of trust. Etc. In my experience, those who have the worst ideas, who have no understanding of what it takes to execute said idea, are generally the ones who shove an NDA in my face before I even say, "Hello."
https://github.com/mjhea0/pinky-promise https://github.com/mjhea0/pinky-promise
- moron4hire 12y agoI'm actually an everything-developer and some of the wording of this particular document isn't clear on how anyone would prove whether or not I had access to the non-UI parts of the project, so how would I even go do non-UI work for someone else and still be in compliance? One point I saw expressed in the past on NDAs is that, if you don't know anything about the project before signing, how do you know you don't already have a conflict of interest? I'd be fine if the NDA covered a much more limited scope (say, it covered only official trade secrets and patents) and it came as part of an actual work contract. But to start a discussion with an NDA... Is this just to be expected, that there is a high degree of amateur-hour shenanigans like this and I just have to slog through them? I'm fine with slogging, but I can see my wife getting anxious if I'm turning down most projects that come my way.