4 ms·
I respect Joel immensely. That said, I found his post strange in what it leaves out. So much so that I wrote my own follow up. https://medium.com/@wwalser/re-d
by wwalser 10y ago
I respect Joel immensely. That said, I found his post strange in what it leaves out. So much so that I wrote my own follow up.
https://medium.com/@wwalser/re-developers-side-projects-3ee3274f39fe#.vzp6lcp1r https://medium.com/@wwalser/re-developers-side-projects-3ee3...
Basically, yes, it's standard practice but in every company that I've worked for there have been escape hatches that were relatively easy to utilize. HR usually has paperwork that both parties sign saying something along the lines of "[developer] is going to build [thing] in their own time using their own hardware. We grant [developer] the legal right to maintain ownership of [thing]".
I pay a lot of attention to what I'm signing. My side projects are important to me. They're a part of my lifestyle. I think most devs could very comfortably sign without a second thought. On the whole, state and contract law in the US combine to create a fairly good safety net for avoiding truly abhorrent contracts.
- gkop 10y agoA third perspective: After living and working in California for 6 years, I was considering a job as third engineer at a startup in another state. I was a bit anxious about side projects, and asked about them after receiving the offer. The response was basically what you said, a pleasant surprise, not scary like Joel warned. But for piece of mind, if I took the job, I would still want to find a lawyer in the new state to review the paperwork, which is a drag. In the end I chose to remain in CA, and it's nice. It's nice to completely not ever have to worry about this issue at all. So I get why Joel is resentful after working for years in states where unreasonable invention assignment clauses are enforceable.