I would have to agree with the essence of Malor's comment. But to add to that, it is not a purely Japanese phenomenon to only report good news to superiors.
Having worked at multiple large corporations, it is very common to spin the news. "Yes Mr VP, we always call back within 15 minutes per process" Just don't mention that the call was to tell the person that they were going to have to wait another hour or two for real help.
After reading the article and some of the threads, I can't help but think of a HHGTG quote:
"... were mostly concerned with the movements of little pieces of paper. Which is strange because, on the whole, it wasn't the little pieces of paper that were unhappy...."
An even better analogy than the F-1 in traffic is doing a straight comparison to a pickup.
Give the racer and the pickup each a load to haul. The racing car will pass the pickup several times hauling the load, but the truck driver will be twiddling his thumbs waiting for the other guy to finish.
While Sun boxen are only decent at CPU power, that was not the central design goal. Pushing data is.
Further than this, there is a much larger problem that comes with this remote admin. We are experimenting with remote diagnostics, but are not going to go into remote admin. The reason is: who is liable?
If we were logged in doing something, and a problem occurred, we are liable for it. Proving otherwise can be virtually impossible. Doesn't matter what happened or how it did.
And from the company's standpoint, that is too great of a risk to take. I can't say I disagree either.
All of the comments so far seem to argue that whiplash is going to be a problem. I don't see how that would neccessarily be true as most all of the people I play with/against (and myself as well) instinctively dodge incoming shots well before the fingers get any ideas of following suite. This could be great if it uses as little cpu overhead as it claims.
>There's no valid ethical reason to restrict
>its diffusion by patenting its presentation.
CRC didn't patent it's presentation, they copyrighted it.
While the facts and theories presented by Eric's encyclopedia were public domain, the manner of presentation of those facts and theories is copyrightable by both law and precedent.
This is probably why they were suing him. The only way to decide if his encyclopedia was too similar is to let the courts decide.
Where I work, (large library mfg) we have a relatively decent arrangement worked out. For every shift (standard 8-hrs) that I carry a pager, I get about half an hour's worth of pay. So I get an hour per weekday and an hour and a half per weekend day.
Any time spent on calls is charged normally, which usually results in it being paid as overtime, but even the salaried guys get straight time above their base for it.
It's worked well for the last several years, and I haven't ever heard any real complaints about the system, just the accounting weenies that can't figure it out. Oh well...;-)
=Alert. Alert. Please step away from the sig line.=
Slashdot Mirror
I would have to agree with the essence of Malor's comment. But to add to that, it is not a purely Japanese phenomenon to only report good news to superiors.
Having worked at multiple large corporations, it is very common to spin the news. "Yes Mr VP, we always call back within 15 minutes per process" Just don't mention that the call was to tell the person that they were going to have to wait another hour or two for real help.
Way too common.
After reading the article and some of the threads, I can't help but think of a HHGTG quote:
..."
"... were mostly concerned with the movements of little pieces of paper. Which is strange because, on the whole, it wasn't the little pieces of paper that were unhappy.
An even better analogy than the F-1 in traffic is doing a straight comparison to a pickup.
Give the racer and the pickup each a load to haul. The racing car will pass the pickup several times hauling the load, but the truck driver will be twiddling his thumbs waiting for the other guy to finish.
While Sun boxen are only decent at CPU power, that was not the central design goal. Pushing data is.
OlympicSponsor wrote:
>The problem is where to put it
That one's easy. Just burn it. It all just goes away then...
Further than this, there is a much larger problem that comes with this remote admin. We are experimenting with remote diagnostics, but are not going to go into remote admin. The reason is: who is liable?
If we were logged in doing something, and a problem occurred, we are liable for it. Proving otherwise can be virtually impossible. Doesn't matter what happened or how it did.
And from the company's standpoint, that is too great of a risk to take. I can't say I disagree either.
All of the comments so far seem to argue that whiplash is going to be a problem. I don't see how that would neccessarily be true as most all of the people I play with/against (and myself as well) instinctively dodge incoming shots well before the fingers get any ideas of following suite. This could be great if it uses as little cpu overhead as it claims.
>There's no valid ethical reason to restrict
>its diffusion by patenting its presentation.
CRC didn't patent it's presentation, they copyrighted it.
While the facts and theories presented by Eric's encyclopedia were public domain, the manner of presentation of those facts and theories is copyrightable by both law and precedent.
This is probably why they were suing him. The only way to decide if his encyclopedia was too similar is to let the courts decide.
(Of course, as usual, IANAL)
Where I work, (large library mfg) we have a relatively decent arrangement worked out. For every shift (standard 8-hrs) that I carry a pager, I get about half an hour's worth of pay. So I get an hour per weekday and an hour and a half per weekend day.
;-)
Any time spent on calls is charged normally, which usually results in it being paid as overtime, but even the salaried guys get straight time above their base for it.
It's worked well for the last several years, and I haven't ever heard any real complaints about the system, just the accounting weenies that can't figure it out. Oh well...
=Alert. Alert. Please step away from the sig line.=
Yes, Microsoft has now set their sights on Unix and is hoping to do to Unix what they did to Novell with the same idea.
Some of the things included are NFS share support and NIS+ integrated into Active Directory.
For just the cost of the NT resource kit, you may be able to retain some control without riling management to badly.
Just my $0.02