Needless to say, this is horribly, horribly stupid on so many levels... It may be worth trying to find out whether it's even legal in your jurisdiction.
Anyway and apart from that, if you can, find colleagues who feel the same, and take a stand against it. Try to explain to the management that this is a stupid decision for the company as well. Don't sign anything: A policy like that would probably have to be amended to your work contract to be binding. Chances are, the risk of losing good employees over this outweighs the security they think they get from it.
If there's really nothing that can be done, and you are very unhappy with this (I would be), consider looking for a new job.
As an afterthought, if the practice of limiting your employees' rights to this extent is clearly illegal in your jurisdiction, it could be that simply making them aware of this might stop this without any further trouble.
All companies for which I have worked allowed outside work provided:
no company resources were used (this includes time)
the product of that effort did not directly conflict with the company's interest
the product was not based off of work or specific knowledge gained while working for the company
Typically, companies have a clause in your employment agreement that states that you will inform them when you begin work on outside projects and inform them of the nature so they can approve/deny. In such cases, you want to get that approval in writing.
In your case, this is a pretty difficult situation if this was part of your employment agreement. Even if it isn't, they can fire you for it if your employment is at-will and they find out. Unfortunately, in your situation, you seem to have one of four options:
Convince management that they are being unreasonable.
Fly under the radar and hope you don't get caught.
Find a new job.
Quit and just work on the apps full-time.
If your job is to put out apps in an appstore, though, there's really no way to argue that your outside development of apps for the same appstore isn't a conflict of interest in some respect. If I had to guess, I'd say that either this is the case or you're working for a development manager that doesn't understand the mindset of developers and how they like to tinker and learn outside of work.
While this example sounds a little draconian, it is not uncommon for companies to have some kind of policy regarding outside work. However, this is typically to protect the company from your mistakes rather than to protect them from your departure. If they're that concerned about employees leaving, they should go out of their way to make it the sort of place you would want to stay.
EDIT: I just found this today on a completely unrelated blog, but it totally rings true to this discussion. It's about 11 minutes long, but very entertaining and makes you think too. http://www.youtube.com/watch?v=u6XAPnuFjJc&feature=player_embedded The TL;DR (TL;DW?): Once you get outside the realm of purely physical tasks, organizations that assume you are motivated by money, hands-on direction, etc. will not accomplish their goals nearly as easily as those that assume you are motivated by desires for autonomy (self-direction, self-management), mastery (getting better at doing something) and contribution to something bigger than yourself.
I believe there was a similar pointless rule when I was under the corporate yoke. I think these rules are pointless, backward and wrong. Instead of keeping their developers management pushes them to look for new managment, well, at least the passionate and talented ones.
Check your local labor laws. In California, this kind of thing is blatantly illegal.
The policy enumerated by Shaun is reasonable, and something very similar has been in place at most of my previous employers. The one place that tried something like this was quickly pointed at the statute by knowledgable developers, and the "policy" quietly went away.
But if your job is as a computer programmer, you're almost guaranteed to have something in your employment contract stating that any software you write either in work or outside of work is owned by the company.
If you get written permission from HR and your manager, then if you were to make millions from you out of hours projects, then it would be more difficult for your employer to just take ALL those millions off of you.
发布评论
评论（8）
不用说，这在很多层面上都是非常非常愚蠢的……可能值得尝试找出它在您所在的管辖范围内是否合法。
无论如何，除此之外，如果可以的话，找到有相同想法的同事，并采取反对的立场。尝试向管理层解释这对公司来说也是一个愚蠢的决定。不要签署任何东西：类似的政策可能需要修改到您的工作合同中才能具有约束力。很可能，因此而失去优秀员工的风险超过了他们认为从中获得的安全感。
如果确实无能为力，并且您对此非常不满意（我会的），请考虑寻找新工作。
事后想想，如果在您的管辖范围内将员工权利限制到这种程度显然是非法的，那么只需让他们意识到这一点就可以阻止这种情况，而不会产生任何进一步的麻烦。
Needless to say, this is horribly, horribly stupid on so many levels... It may be worth trying to find out whether it's even legal in your jurisdiction.
Anyway and apart from that, if you can, find colleagues who feel the same, and take a stand against it. Try to explain to the management that this is a stupid decision for the company as well. Don't sign anything: A policy like that would probably have to be amended to your work contract to be binding. Chances are, the risk of losing good employees over this outweighs the security they think they get from it.
If there's really nothing that can be done, and you are very unhappy with this (I would be), consider looking for a new job.
As an afterthought, if the practice of limiting your employees' rights to this extent is clearly illegal in your jurisdiction, it could be that simply making them aware of this might stop this without any further trouble.
我工作过的所有公司都允许外出工作，前提是：
通常情况下，公司在您的雇佣协议中会有一项条款，规定您将在开始从事外部项目时通知他们，并告知他们项目的性质，以便他们批准/拒绝。在这种情况下，您希望获得书面批准。
就您而言，如果这是您就业协议的一部分，那么情况会非常困难。即使不是，如果你的工作是随意的并且他们发现了，他们也可以解雇你。不幸的是，在您的情况下，您似乎有四个选择之一：
但是，如果您的工作是在应用程序商店中发布应用程序，那么确实没有办法证明您为同一应用程序商店进行的外部开发在某些方面不存在利益冲突。如果我不得不猜测，我会说，要么是这种情况，要么你正在为一位开发经理工作，他不了解开发人员的思维方式以及他们如何喜欢在工作之外修补和学习。
All companies for which I have worked allowed outside work provided:
Typically, companies have a clause in your employment agreement that states that you will inform them when you begin work on outside projects and inform them of the nature so they can approve/deny. In such cases, you want to get that approval in writing.
In your case, this is a pretty difficult situation if this was part of your employment agreement. Even if it isn't, they can fire you for it if your employment is at-will and they find out. Unfortunately, in your situation, you seem to have one of four options:
If your job is to put out apps in an appstore, though, there's really no way to argue that your outside development of apps for the same appstore isn't a conflict of interest in some respect. If I had to guess, I'd say that either this is the case or you're working for a development manager that doesn't understand the mindset of developers and how they like to tinker and learn outside of work.
虽然这个例子听起来有点严厉，但公司对外部工作制定某种政策的情况并不罕见。然而，这通常是为了保护公司免受你的错误影响，而不是保护他们免受你的离职影响。如果他们担心员工离开，他们应该竭尽全力让这里成为你想要留下来的地方。
编辑：我今天刚刚在一个完全不相关的博客上发现了这个，但它完全符合这个讨论。片长约 11 分钟，但非常有趣，也能让你思考。 http://www.youtube.com/watch?v=u6XAPnuFjJc&feature= player_embedded TL;DR（TL;DW？）：一旦你脱离了纯粹体力任务的领域，那些认为你的动机是金钱、亲力亲为等的组织将不会像以前那样实现他们的目标。就像那些假设你的动机是渴望自主（自我指导、自我管理）、掌握（在做某事上做得更好）以及为比自己更大的事情做出贡献一样。
While this example sounds a little draconian, it is not uncommon for companies to have some kind of policy regarding outside work. However, this is typically to protect the company from your mistakes rather than to protect them from your departure. If they're that concerned about employees leaving, they should go out of their way to make it the sort of place you would want to stay.
EDIT: I just found this today on a completely unrelated blog, but it totally rings true to this discussion. It's about 11 minutes long, but very entertaining and makes you think too. http://www.youtube.com/watch?v=u6XAPnuFjJc&feature=player_embedded The TL;DR (TL;DW?): Once you get outside the realm of purely physical tasks, organizations that assume you are motivated by money, hands-on direction, etc. will not accomplish their goals nearly as easily as those that assume you are motivated by desires for autonomy (self-direction, self-management), mastery (getting better at doing something) and contribution to something bigger than yourself.
我相信当我在公司的枷锁下时也有类似的毫无意义的规则。我认为这些规则是毫无意义的、落后的和错误的。他们没有保留开发人员管理，而是寻找新的管理人员，至少是充满热情和才华横溢的管理人员。
I believe there was a similar pointless rule when I was under the corporate yoke. I think these rules are pointless, backward and wrong. Instead of keeping their developers management pushes them to look for new managment, well, at least the passionate and talented ones.
除非您的雇佣合同另有规定，否则您在自己的时间内开发的成果属于您。
如果他们从事为应用程序商店编写应用程序的业务，那么他们可能会对您提出非竞争论点。
如果他们允许其他类型的开发项目，则很难认为该论点有效。
Unless your employment contract says otherwise, what you develop in your own time belongs to you.
If they are in the business of writing apps for the appstore, then they might have a non-compete argument against you.
If they allow other types of development projects, it is difficult to see the argument as valid.
取决于应用程序和公司。
如果您为 Android 应用程序开发人员工作，我会明白为什么他们可能不喜欢它。 8)
如果它与你们公司生产的产品直接竞争，我可以理解为什么他们会禁止它。
我会咨询律师，看看如果你被迫签署这样的协议，它的约束力有多大。
如果真的那么令人厌恶，你唯一的办法就是另找雇主。
Depends on the app and the company.
If you're working for an Android app developer, I'd see why they might not like it. 8)
If it competes directly with what your company produces I can see why they'd prohibit it.
I would consult a lawyer to see just how binding such an agreement would be if you were forced to sign it.
If it's really that odious, your only recourse is to find another employer.
检查您当地的劳动法。在加州，这种事情是公然违法的。
肖恩列举的政策是合理的，我以前的大多数雇主也采取了非常相似的政策。尝试类似做法的一个地方很快就被知识渊博的开发商指出了该法规，“政策”就悄然消失了。
Check your local labor laws. In California, this kind of thing is blatantly illegal.
The policy enumerated by Shaun is reasonable, and something very similar has been in place at most of my previous employers. The one place that tried something like this was quickly pointed at the statute by knowledgable developers, and the "policy" quietly went away.
答案就在您的雇佣合同中。
但是，如果您的工作是计算机程序员，那么您几乎可以保证在雇佣合同中注明您在工作中或工作之外编写的任何软件均归公司所有。
如果你得到了人力资源部和经理的书面许可，那么如果你想从你的非工作时间项目中赚取数百万美元，那么你的雇主就更难从你身上拿走所有这些数百万美元。
The answer is in your contract of employment.
But if your job is as a computer programmer, you're almost guaranteed to have something in your employment contract stating that any software you write either in work or outside of work is owned by the company.
If you get written permission from HR and your manager, then if you were to make millions from you out of hours projects, then it would be more difficult for your employer to just take ALL those millions off of you.