Interviewer: What about this gap here in your employment history? Interviewee: I plead the fifth, on the grounds that answering that question might serve to incriminate me. Interviewer: Okay, then...NEXT.
I would look seriously askance at someone so mercenary as to stay in a morally bankrupt organization, like a Monsanto or a Nike or an SCO or such.
Hence, hiring managers ought to look favorably on those trying to get out. Present or prior affiliation with the company is no basis for character assassination. Continued affiliation is rightly questionable; but, still not a reasonable lone basis for judging character.
Just because someone has worked there beyond May 2003, it does not mean they are part of the problem. I find it reasonable to expect someone working there could have started a job search in May and still be looking for a new job today.
Is it fair to penalize them further simply because they haven't been able to transition to a new place of employ in the interim? I can't fault them for thinking going in and collecting a paycheck is better than going home and not...all while searching for a new job.
Perhaps the better course of action would be to post to your HR page that continued employment with SCO beyond May 2003 could cast doubt on your character and the longer you stay at SCO the more it hurts your chances of finding other employment...but still accepting the resumes.
In fact, I think it may be prudent for people in search of technical talent to recruit out of SCO. I don't imagine technically competent, quality employees are eager to stay, if there are any left.
Of course that's just my opinion; I could be wrong.
The problem with this "IP warranty" is really that what he means is indemnification. IBM will not indemnify you against third party legal claims in regards to Linux.
But indemnification is a red herring. When you purchase software from any vendor, the EULA is the closest thing you get to a contract. Most EULAs explicitly disclaim any and every possible warranty "whether express or implied" up to and including the basic idea that the software does what it is "supposed" to do.
I've read over my Windows 2000 EULA and there is ZERO verbage about indemnification.
I doubt anybody will indemnify you from third-party legal claims. Look at Microsoft and the recent Internet Explorer plug-in patent violation ruling. Do I have a signed, enforceable contract from Microsoft that guarantees they will protect me from somebody coming after me because I continue to use the version of IE (god forbid) that violates their patent(s)? NO. Will MSFT give me one? Not bloody likely.
In the spirit of open source, I would point out that you have the ability to do this yourself. That's one of the benefits of open source over closed source: in the closed source world, you bitch and moan about things, but can do little else; whereas, in the open source world, you can bitch and moan about things, and people will tell you to STFU and do it yourself if you want it so bad.
Welcome to the revolution.
Re:It's not MS targetting SGI, it really *is* SCO
on
SCO's Next Target: SGI?
·
· Score: 4, Informative
Three or four years ago, UnixWare was actually functionally superior to Linux
I will concede you may know better than I do; but, I used Linux three (and four) years ago and I disagree. It is highly subjective whether UnixWare was functionally superior to Linux. Is a hammer functionally superior to a screwdriver? It depends entirely on what function you are after.
It's a rational move for them.
It appears to me their entire case hinges on how "derivative work" is defined. The SCO position, however, does not appear rational.
The contract language as I read it (IANAL) would indicate a derivative work is the *entirety* of an OS based on the SVR4 source. Thus, IRIX, or AIX in its entirety must be treated the same as the SVR4 source...and therefore cannot be released publicly or GPL-ed in its entirety.
But JFS, XFS, NUMA, RCU, et. al. are not the entire derivative work that is AIX, IRIX, and/or Dynix/ptx. They are components. Components designed and developed by their respective copyright holders...not SCO.
I find it irrational that SCO would believe they stand a chance of convincing any competent judge that the contract language defines components like file systems, and what essentially amounts to drivers (imho) as derivative works.
SCO's conviction may be they will not meet a competent judge.
forget vibrate on your cell, download cool polyphonic ring tones...turn the ring volume all the way up
Have meetings in your cubicle. No need to waste conference room space
Enable stupid event sounds on your PC and turn the volume up. Use southpark or similar themes
Talk to yourself
laugh out loud for no apparent reason
Even better, learn to make that "snort" sound when you laugh
belch, pass gass, etc.
as a follow up to gas, shout "he who smelt it delt it!"
Throw spitballs over the cubicle walls
Find a willing accomplice and pass a tennis ball or football or something like that to one another over the cubicle wall
wear a lot of cologne or perfume
preferrably, perfume...especially if you're a guy...
post on slashdot all day, but turn your monitor so it's harder to see when people walk by your desk
always keep a spreadsheet or development session open in the background to switch to in the event someone actually expresses interest in what you're doing
I suffer from clinical depression. I believe that to be mostly attributable to my employment situation.
I am looking for a new position and it is tough right now. Which contributes to my depression. I could get a new job easier if I could live on less money...which is also easier said than done with three kids...one with a genetic disorder requiring OT,PT,ST,etc.
It is a privately held company, so no worries on your stock. I would like to think this place could never get past the SEC to get listed in the first place, but that's probably what's left of my optimism speaking.
Although I try to stay above the fray, be honorable and professional, I can't help but have a part of me--in that darkest of deep dark places--that would be exhuberantly joyful if it did crash and burn.
I try. I am currently working on a project that I started two months ago. If I dedicated myself to it full time, I believe I could have completed it in under a month. So I figured it would take two. We are still barely able to get it done on time...and really it's not done because we had to bump some documentation and reports. I don't think it's because I am a bad estimator or because I can't get things done. I believe it's because at various times over the past two months, I've been pulled off of this project by the CFO multiple times, and by the CEO yet other times.
Always, make sure you have proper backing on it
Aye, there's the rub. I told the CFO last time he pulled me off of this project it would back it up at least a week. He told me, in the presence of others, "Fine...I'll give you five days for this."
Then, we had a meeting last Friday to go over the schedule and guess what...those five days are gone. I don't get them. Management backing is the one thing I've been harping on the most for the last year. They've got to buy in, and force the vision on the users who keep pushing back simply because "Oh, my God! IT'S DIFFERENT!!!"
I have had meetings with the CFO and owner where we agree on the direction of the project (we'll do X, but not Y, etc.) and then go over this with the controller, who whines about Y, and then the CFO will
Present it as I.T.'s decision
Backpedal
Waffle
Change direction
Act like he knew nothing about it
desroy I.T. credibility
and really, really piss me off
Oh, the President and the CEO/Owner...same thing. And one other thing: nepotism...look it up.
Basically, it is my educated opinion that they don't know what the f* they're doing, only hold the position because they are related to the original founder, are mostly good at covering their asses (and little else), and blame I.T. for pretty much everything that ever goes wrong. Even when it's a power outage. Jesus, I'm tired of getting asked questions like: "So, how long until the power is restored?" What the f* am I, an electrician? Call AEP, moron.
I like that. Especially making them say stupid things. That might get the wheels turning and thinking about true priorities.
I can't remember where I read it, but I just thought of a saying to the effect of: when everything is top priority, nothing is. I've tried explaining that, to no avail.
Upper management types are usually not planners per-se, they are *negotiators*, and unless you find a way to push back you're going to get fsck'd.
That's the first time I've ever heard it put that way, and it's damn insightful. The problem I always run up against is the CFO and CEO are constantly rearranging what the "#1" priority is. Today it's project X, but tomorrow it will be something else...and next week it will be project X again. Then they'll complain that I didn't get project X done last week.
I understand priorities; but changing a company's culture (as this person will need to do to be successful) is a difficult task. It's not about prioritizing: it's about changing the process. We (I.T.) struggle with it so much at my place of work. Trying to get upper management to work with us on setting priorities and sticking to them is terribly difficult when the owner and associated YES!-people have "shiny-thing" syndrome.
Injecting structure into a process that for the last 20 years has had little formality is (IMHO) a gargantuan task...
Greatest movie ending ever? How many movies have you actually *seen*? The matrix reloaded would have been much better had the directer/producer/editor/somebody with some sense ended it 30 seconds sooner. I can't express well enough my utter disdain for that ending. What are we, morons? We have to be fed that crap at the end? For all it's ups & downs, I enjoyed the movie...but seriously, that last 30 seconds just completely ruined it. They could have just cut it after Neo stopped the sentinals...or at least after showing him on the table.
Everything after that was just explaining things for the *slow* members of the audience.
I have ~ 15 years of technical experience and I would love an MBA. Why? So I could have a better idea what goes on in the mind of the CEO. I just don't get the thinking a lot of times.
The education provided in the MBA path is (to me) no more than a window into the vagaries of the management mind. A scary thought, indeed...but who doesn't wonder the "whys" of management?
Does violating the GPL with one product (the kernel) violate it under another (samba)?
That is, could the Samba team actually file against SCO for injunctive relief to prohibit them from distributing Samba for license violation just because they violated the GPL where the Linux kernel is concerned?
Slashdot Mirror
Interviewer: What about this gap here in your employment history?
Interviewee: I plead the fifth, on the grounds that answering that question might serve to incriminate me.
Interviewer: Okay, then...NEXT.
Just because someone has worked there beyond May 2003, it does not mean they are part of the problem. I find it reasonable to expect someone working there could have started a job search in May and still be looking for a new job today.
Is it fair to penalize them further simply because they haven't been able to transition to a new place of employ in the interim? I can't fault them for thinking going in and collecting a paycheck is better than going home and not...all while searching for a new job.
Perhaps the better course of action would be to post to your HR page that continued employment with SCO beyond May 2003 could cast doubt on your character and the longer you stay at SCO the more it hurts your chances of finding other employment...but still accepting the resumes.
In fact, I think it may be prudent for people in search of technical talent to recruit out of SCO. I don't imagine technically competent, quality employees are eager to stay, if there are any left.
Of course that's just my opinion; I could be wrong.
The problem with this "IP warranty" is really that what he means is indemnification. IBM will not indemnify you against third party legal claims in regards to Linux.
But indemnification is a red herring. When you purchase software from any vendor, the EULA is the closest thing you get to a contract. Most EULAs explicitly disclaim any and every possible warranty "whether express or implied" up to and including the basic idea that the software does what it is "supposed" to do.
I've read over my Windows 2000 EULA and there is ZERO verbage about indemnification.
I doubt anybody will indemnify you from third-party legal claims. Look at Microsoft and the recent Internet Explorer plug-in patent violation ruling. Do I have a signed, enforceable contract from Microsoft that guarantees they will protect me from somebody coming after me because I continue to use the version of IE (god forbid) that violates their patent(s)? NO. Will MSFT give me one? Not bloody likely.
LOL...thanks for clearing that up...
In the spirit of open source, I would point out that you have the ability to do this yourself. That's one of the benefits of open source over closed source: in the closed source world, you bitch and moan about things, but can do little else; whereas, in the open source world, you can bitch and moan about things, and people will tell you to STFU and do it yourself if you want it so bad.
Welcome to the revolution.
The contract language as I read it (IANAL) would indicate a derivative work is the *entirety* of an OS based on the SVR4 source. Thus, IRIX, or AIX in its entirety must be treated the same as the SVR4 source...and therefore cannot be released publicly or GPL-ed in its entirety.
But JFS, XFS, NUMA, RCU, et. al. are not the entire derivative work that is AIX, IRIX, and/or Dynix/ptx. They are components. Components designed and developed by their respective copyright holders...not SCO.
I find it irrational that SCO would believe they stand a chance of convincing any competent judge that the contract language defines components like file systems, and what essentially amounts to drivers (imho) as derivative works.
SCO's conviction may be they will not meet a competent judge.
look
That's all I'm sayin...
Huh? ... wha?
See here for response.
- I suffer from clinical depression. I believe that to be mostly attributable to my employment situation.
- I am looking for a new position and it is tough right now. Which contributes to my depression. I could get a new job easier if I could live on less money...which is also easier said than done with three kids...one with a genetic disorder requiring OT,PT,ST,etc.
- It is a privately held company, so no worries on your stock. I would like to think this place could never get past the SEC to get listed in the first place, but that's probably what's left of my optimism speaking.
- Although I try to stay above the fray, be honorable and professional, I can't help but have a part of me--in that darkest of deep dark places--that would be exhuberantly joyful if it did crash and burn.
peace...Then, we had a meeting last Friday to go over the schedule and guess what...those five days are gone. I don't get them. Management backing is the one thing I've been harping on the most for the last year. They've got to buy in, and force the vision on the users who keep pushing back simply because "Oh, my God! IT'S DIFFERENT!!!"
I have had meetings with the CFO and owner where we agree on the direction of the project (we'll do X, but not Y, etc.) and then go over this with the controller, who whines about Y, and then the CFO will
- Present it as I.T.'s decision
- Backpedal
- Waffle
- Change direction
- Act like he knew nothing about it
- desroy I.T. credibility
- and really, really piss me off
Oh, the President and the CEO/Owner...same thing. And one other thing: nepotism...look it up.Basically, it is my educated opinion that they don't know what the f* they're doing, only hold the position because they are related to the original founder, are mostly good at covering their asses (and little else), and blame I.T. for pretty much everything that ever goes wrong. Even when it's a power outage. Jesus, I'm tired of getting asked questions like: "So, how long until the power is restored?" What the f* am I, an electrician? Call AEP, moron.
Sorry for the rant...
I like that. Especially making them say stupid things. That might get the wheels turning and thinking about true priorities.
I can't remember where I read it, but I just thought of a saying to the effect of: when everything is top priority, nothing is. I've tried explaining that, to no avail.
I understand priorities; but changing a company's culture (as this person will need to do to be successful) is a difficult task. It's not about prioritizing: it's about changing the process. We (I.T.) struggle with it so much at my place of work. Trying to get upper management to work with us on setting priorities and sticking to them is terribly difficult when the owner and associated YES!-people have "shiny-thing" syndrome.
Injecting structure into a process that for the last 20 years has had little formality is (IMHO) a gargantuan task...
Yes, you and the other three of us.
Hence, no series.
I'm sorry...
"To be continued..."
Greatest movie ending ever? How many movies have you actually *seen*? The matrix reloaded would have been much better had the directer/producer/editor/somebody with some sense ended it 30 seconds sooner. I can't express well enough my utter disdain for that ending. What are we, morons? We have to be fed that crap at the end? For all it's ups & downs, I enjoyed the movie...but seriously, that last 30 seconds just completely ruined it. They could have just cut it after Neo stopped the sentinals...or at least after showing him on the table.
Everything after that was just explaining things for the *slow* members of the audience.
Lives are arguably not profitable. Copyright is.
No it doesn't.
I have ~ 15 years of technical experience and I would love an MBA. Why? So I could have a better idea what goes on in the mind of the CEO. I just don't get the thinking a lot of times.
The education provided in the MBA path is (to me) no more than a window into the vagaries of the management mind. A scary thought, indeed...but who doesn't wonder the "whys" of management?
Didn't SCO just announce the other day a new product that would be distributed with Samba 3.0? I know I read that somewhere...
Ahh, yes...there's this and this.
Does violating the GPL with one product (the kernel) violate it under another (samba)?
That is, could the Samba team actually file against SCO for injunctive relief to prohibit them from distributing Samba for license violation just because they violated the GPL where the Linux kernel is concerned?
Check out lout. I found it easier to work with than LaTeX. YMMV.
If you can wait, you may also consider using Jeff's followup to lout, Nonpareil. The specs are done, but he's still working on a compiler.
And you know why that is? I think I know: people suck.