Chances are your employment agreement states that anything you invented while employed with your company is the sole property of your company.
Employment agreements are actually pretty crappy in this regard. If you had a million dollar idea that was completely unrelated to your work/employer, and even if you develop it on your "own time", quit, go into business by yourself, etc... your (former) employer could actually sue you and win.
With regard to ethics, if 100% of your project is closed source, by refusing to assist the company with a patent you're basically being insubordinate and refusing to do part of your job. A company has every right to patent and protect their IP.
Patents don't have to stifle innovation. They're used to protect ideas and a company's ability to make money. Doesn't a company have that right?
Also, look at the MPEG consortium. MPEG is a patented technology. If you use the technology in a commercial application, you must license the technology. But you can still write encoders and decoders and distribute the source freely for educational and personal use. Why shouldn't the members of the consortium be entitled to a piece of the pie? And we, as knowledge thirsty hackers, still get to learn all we want.
On the other hand, if some piece of the project is open source, I think it is important that your employer respect all the terms of the relevant public license. In this regard you should explain the principles of the matter. If they don't abide, you could actually go to the FSF or something.
In either case, either party's refusal to comply with their duties will quickly lead to your resignation.
Maybe it sounds cheesy to us, but between my own kids and my nieces and nephews, I find they're totally infatuated with my Atari 130XE.
BASIC obviously has its flaws, but BASIC serves its purpose well: BEGINNERS all purpose....
IMHO, your teenager could learn the fundamentals of programming and logic. Learn a little history, gain an appreciation for the difference between 128K and 4GB, etc. And if you can structure code well in BASIC, you're set for life!:)
As a side benefit, you could also have fun playing some vintage games when you're not hacking away...
That's a crappy attitude that will land you the reputation of "pessimistic bastard" of the organization. It certainly isn't productive for you or the company in the long run.
It is true that public companies will not think twice about trimming the fat when push comes to shove (and all the savings goes into the CEO's bonus check).
There are two ways two avoid being trimmed fat:
1. be a key contributor
2. be helpful to your co-workers
Neither of which require working 80 hours/week. Be smart. Be quick. Be productive. Have fun. Be funny. Learn.
If you can't do all of the above, then get another job.
While I suspect the newbie grad can't take credit for the brain-child of his boss, I'm sure he learned a lot in the process. If he had fun and got paid, what more can he ask?
Slashdot Mirror
Chances are your employment agreement states that anything you invented while employed with your company is the sole property of your company. Employment agreements are actually pretty crappy in this regard. If you had a million dollar idea that was completely unrelated to your work/employer, and even if you develop it on your "own time", quit, go into business by yourself, etc... your (former) employer could actually sue you and win. With regard to ethics, if 100% of your project is closed source, by refusing to assist the company with a patent you're basically being insubordinate and refusing to do part of your job. A company has every right to patent and protect their IP. Patents don't have to stifle innovation. They're used to protect ideas and a company's ability to make money. Doesn't a company have that right? Also, look at the MPEG consortium. MPEG is a patented technology. If you use the technology in a commercial application, you must license the technology. But you can still write encoders and decoders and distribute the source freely for educational and personal use. Why shouldn't the members of the consortium be entitled to a piece of the pie? And we, as knowledge thirsty hackers, still get to learn all we want. On the other hand, if some piece of the project is open source, I think it is important that your employer respect all the terms of the relevant public license. In this regard you should explain the principles of the matter. If they don't abide, you could actually go to the FSF or something. In either case, either party's refusal to comply with their duties will quickly lead to your resignation.
Maybe it sounds cheesy to us, but between my own kids and my nieces and nephews, I find they're totally infatuated with my Atari 130XE. BASIC obviously has its flaws, but BASIC serves its purpose well: BEGINNERS all purpose.... IMHO, your teenager could learn the fundamentals of programming and logic. Learn a little history, gain an appreciation for the difference between 128K and 4GB, etc. And if you can structure code well in BASIC, you're set for life! :)
As a side benefit, you could also have fun playing some vintage games when you're not hacking away...
That's a crappy attitude that will land you the reputation of "pessimistic bastard" of the organization. It certainly isn't productive for you or the company in the long run. It is true that public companies will not think twice about trimming the fat when push comes to shove (and all the savings goes into the CEO's bonus check). There are two ways two avoid being trimmed fat: 1. be a key contributor 2. be helpful to your co-workers Neither of which require working 80 hours/week. Be smart. Be quick. Be productive. Have fun. Be funny. Learn. If you can't do all of the above, then get another job. While I suspect the newbie grad can't take credit for the brain-child of his boss, I'm sure he learned a lot in the process. If he had fun and got paid, what more can he ask?