John Glenn lost all credibility with me when, as a US senator, he pulled that garbage line about "exploring the effects of age on space travel" as an excuse to get NASA to launch him back to space.
He was once part of a band of heros. Now he's just another politician.
I'm glad to see that at least someone has the guts to stand up for their personal time. I once worked in an applications support team where, as our boss put it, we were always "on call 24/7/365"
I ditched that job six months ago. It's fine if you're going to be "on call" at scheduled, planned times. I will not submit to an employer who thinks that they own me. Unfortunately, there were a lot of "sheeple" at the job who just took it. (I guess they're the ones making life hard for the rest of us!?)
In short, poor planning on my employers part should not necessitate an emergency on my part.
I've decided that employment agreements that define intellectual property rights and disclosure really don't amount to much. Every employment agreement that I've read always has language about disclosing "work related" inventions and the company's right to those inventions.
Developers that I've worked with tend to construe those paragraphs very broadly and sometimes get themselves really worked up over the possibality of their employer stealing their million dollar invention. The thing about that is that if a company and employee were ever to get in a legal spat over IP, then most judges and jurys are going to be able to see the dividing line.
The bottom line is to use common sense. If you're employed writing software to analyize widgets and you write a directly competing product on the side, then you obiviously have no case to say that it's not work related. On the other hand, most judges and jurys can see enough difference between widget analysis and personal accounting that they're not going to let a company sue you just because you wrote in the same language and used similar coding practices on your personal time.
I was on the SCO earnings call yesterday. Darl and his merry band of lawyers repeatedly refused to release any technical details, citing the judge's orders.
John Glenn lost all credibility with me when, as a US senator, he pulled that garbage line about "exploring the effects of age on space travel" as an excuse to get NASA to launch him back to space.
He was once part of a band of heros. Now he's just another politician.
Don't underestimate yourself, esteemed
Except that I worked there in 2000 when we didn't get that leap year.
I'm glad to see that at least someone has the guts to stand up for their personal time. I once worked in an applications support team where, as our boss put it, we were always "on call 24/7/365"
I ditched that job six months ago. It's fine if you're going to be "on call" at scheduled, planned times. I will not submit to an employer who thinks that they own me. Unfortunately, there were a lot of "sheeple" at the job who just took it. (I guess they're the ones making life hard for the rest of us!?)
In short, poor planning on my employers part should not necessitate an emergency on my part.
Thanks for letting me rant, too.
I've decided that employment agreements that define intellectual property rights and disclosure really don't amount to much. Every employment agreement that I've read always has language about disclosing "work related" inventions and the company's right to those inventions.
Developers that I've worked with tend to construe those paragraphs very broadly and sometimes get themselves really worked up over the possibality of their employer stealing their million dollar invention. The thing about that is that if a company and employee were ever to get in a legal spat over IP, then most judges and jurys are going to be able to see the dividing line.
The bottom line is to use common sense. If you're employed writing software to analyize widgets and you write a directly competing product on the side, then you obiviously have no case to say that it's not work related. On the other hand, most judges and jurys can see enough difference between widget analysis and personal accounting that they're not going to let a company sue you just because you wrote in the same language and used similar coding practices on your personal time.
I was on the SCO earnings call yesterday. Darl and his merry band of lawyers repeatedly refused to release any technical details, citing the judge's orders.
I guess that this the judge's response!
I dialed in 40 minutes early. I want the best seat in the house.
Sure free trade helps megacorps.
And guess who works for the megacorps? Most of the people I know who have the best jobs, IT and otherwise.
Guess who invests in the megacorps? Your mutual funds, 401(k) plans, IRAs.
Megacorps are the people who make most of the stuff that you and I use every day.
If it's good for them, then it's good for you and for me, too.
Band Saw