." This seems like a fair thing to ask for, but how likely is a company to grant such a boon, even if they do want to use your property to run their wires?
Not too likely, IMHO. I've worked for/at two large telcos (hey Wiltel and Sprint, don't miss ya); being the what they are they when you hit 'em up with an out-of-the-box request like that they'll just ignore you. Don't get me wrong, on a personal level, every person you meet may well think it's a great idea, but just try and ram it through their institutional process . .
that her manager simply wanted to tell her in person rather than over the phone while she was away on business, and the machinery got ahead of her. How many of you have seen the wheels of HR grind interminably, in spite of the best interests of the company or the individuals?
Possible, but probably not. If he was that concerned (and the odds are against it, given what the article says about the place) he would have met her and done the business first thing.
I'll second that bit about right to work states - I've gotten at least two months severence when I've been laid off (twice now - thank YOU Sprint Paranet!) but others did not receive as much (thank YOU Compaq).
You're looking for a document that is a guide, not a straitjacket, one that can be interpeted and reinterpeted as your company culture grows and changes.
from a casual reading of the 'serious' posts, some of you may be missing the point.
There will (probably) not be a major conflict between massed armies (ala WW III in Europe). Most conflict will be between 'western' military units and ad-hoc collections of urban warriors, gangs, thugs, jihads, and assorted militias. The conflict will be come as you are, and the OPFOR (the thugs etc.) will be using state of the art commo equipment. Which is vulnerable to the EMP effect.
If the unit commander gets a good fix on the C3 node (sorry, Command, Control and Communications), and he will because the OPFOR may be many things, but probably will not have tight discipline, he can fire off a bracket of these rounds and put that node out of business.
Please don't forget, the goal of a good commander is NOT to kill the enemy, it is to break his heart and make him run for home. You can do this with casualties, but it's so much more elegant to zap his commo . .
good luck getting a user at the site to do so:P
i have enough trouble getting them to send me the monthly tapes. environmental concerns is a major thing to consider
i've had that problem. make sure that the remote site guys have written procedures to follow - and a number to call if anything untword happens. have your senior boss person speak to the senior boss person at the remote site. impress upon both of them that if *they* won't follow your written SOP, then when *their* data goes south, it's going to be a long time to recover. write up a FAQ detailing *how* long it takes to recover, and the revenue lost.
Seriously, *they* don't really see why they are doing what you ask, they don't care. But they do speak 'downtime' and revenue lost, and they *must* understand that you can't wave a magic wand and make it better . .
We have used Quantum DLT 7000s (two of which died), and we have two VXA drives (11 hours to restore three tarballs). Is there a better solution?"
Drives die within about 6-12 months, and tapes die in a few months.
whatinthehell are you people *doing*? clean those drives on a weekly basis, retire you tapes after xx hours of use, and you'll be fine. And for gods sake, using another box for backups is *fine* - until your entire site burns to the ground, and your whooptedoo backup system with it. kids these days.
A friend in Sweden tells me that the U.S.A. is now being referred to as the B.R.A., the Banana Republic of America. Maybe by the 21st century we can have 20th-century voting machines installed at our polling places, what do you think?
I think that in a classic Banana Republic we wouldn't even *have* a meaningfull vote, and that by now the troops would have been called out and the new El Presidante (Gore, he's got the troops already) would have been installed, until the current emergency passes.
'the decision to fire weapons should be made by a human, to reduce the risk of "friendly fire."' This is not logical: Since the planes can be networked and thus know each other's relative positions, preventing friendly fire is a much simpler problem than the visual recognition required to determine what to shoot at, unless you don't mind hitting non-military targets.
It is SO logical - but military logic is oftentimes the converse of 'civilian' logic. Murphy rules on the battlefield, and the idea of a horde of automated machines making fire/don't fire descisions give this ex-grunt the willies. Kids these days....
sample quote "In a relatively democratic system like our own, it's perhaps better if change happens slowly, after much debate. As pointed out to me by the computer scientist David Rosenthal, in governance "slowness is a feature, not a bug."
N. Dean Meyer and Associates has some fascinating how-to books on . . process and management. They not only publish, but the contents are on-line. http://www.ndma.com/
I've read them all (aborted startup from last year) and it seems like a great approach - just great dollaps of common-sense.
the catch is - it must be married to your corporate management process, or everyone involved is spinning their wheels. The best example I've seen was at the Motorola plant in Fort Worth, from my pov (contractor) change was slow, and changes had to be approved by everyone in the world, but that was the way their entire operation worked, so (in that context) it was 'okay' - and it worked.
Slashdot Mirror
Not too likely, IMHO. I've worked for/at two large telcos (hey Wiltel and Sprint, don't miss ya); being the what they are they when you hit 'em up with an out-of-the-box request like that they'll just ignore you. Don't get me wrong, on a personal level, every person you meet may well think it's a great idea, but just try and ram it through their institutional process . .
Possible, but probably not. If he was that concerned (and the odds are against it, given what the article says about the place) he would have met her and done the business first thing.
You're looking for a document that is a guide, not a straitjacket, one that can be interpeted and reinterpeted as your company culture grows and changes.
MrF
There will (probably) not be a major conflict between massed armies (ala WW III in Europe). Most conflict will be between 'western' military units and ad-hoc collections of urban warriors, gangs, thugs, jihads, and assorted militias. The conflict will be come as you are, and the OPFOR (the thugs etc.) will be using state of the art commo equipment. Which is vulnerable to the EMP effect.
If the unit commander gets a good fix on the C3 node (sorry, Command, Control and Communications), and he will because the OPFOR may be many things, but probably will not have tight discipline, he can fire off a bracket of these rounds and put that node out of business.
Please don't forget, the goal of a good commander is NOT to kill the enemy, it is to break his heart and make him run for home. You can do this with casualties, but it's so much more elegant to zap his commo . .
MrF
i've had that problem. make sure that the remote site guys have written procedures to follow - and a number to call if anything untword happens. have your senior boss person speak to the senior boss person at the remote site. impress upon both of them that if *they* won't follow your written SOP, then when *their* data goes south, it's going to be a long time to recover. write up a FAQ detailing *how* long it takes to recover, and the revenue lost.
Seriously, *they* don't really see why they are doing what you ask, they don't care. But they do speak 'downtime' and revenue lost, and they *must* understand that you can't wave a magic wand and make it better . .
Drives die within about 6-12 months, and tapes die in a few months.
whatinthehell are you people *doing*? clean those drives on a weekly basis, retire you tapes after xx hours of use, and you'll be fine. And for gods sake, using another box for backups is *fine* - until your entire site burns to the ground, and your whooptedoo backup system with it. kids these days.
I think that in a classic Banana Republic we wouldn't even *have* a meaningfull vote, and that by now the troops would have been called out and the new El Presidante (Gore, he's got the troops already) would have been installed, until the current emergency passes.
It is SO logical - but military logic is oftentimes the converse of 'civilian' logic. Murphy rules on the battlefield, and the idea of a horde of automated machines making fire/don't fire descisions give this ex-grunt the willies. Kids these days ....
sample quote "In a relatively democratic system like our own, it's perhaps better if change happens slowly, after much debate. As pointed out to me by the computer scientist David Rosenthal, in governance "slowness is a feature, not a bug."
Brazil has been a democracy for, what less than half a century? Less if you count the hunta/dictator cycle endemic to South America.
It's old, yes. It works, yes. It comes to a matter of *TRUST* - you can trust paper and pen/pencil marks. You can't trust computers and web sites.
N. Dean Meyer and Associates has some fascinating how-to books on . . process and management. They not only publish, but the contents are on-line. http://www.ndma.com/
I've read them all (aborted startup from last year) and it seems like a great approach - just great dollaps of common-sense.
Anyone? Hello?
MrF
the catch is - it must be married to your corporate management process, or everyone involved is spinning their wheels. The best example I've seen was at the Motorola plant in Fort Worth, from my pov (contractor) change was slow, and changes had to be approved by everyone in the world, but that was the way their entire operation worked, so (in that context) it was 'okay' - and it worked.
MrF