I have read (hey may as well start of with unsubstantiated factoids right off the bat!) that most estimates yeild results of "only" about 125 - 150 years worth of uranium at current consumption levels.
I am a pretty decent coder, acoording to my bosses. Technical management can only take one so far. An IP lawyer who knows what he is doing should do pretty well (assuming I keep up with technology).
I would code until retirement, but it just doesn't seem realistic for a variety of reasons.
...some are better than others, some are cleaner than others, but we will never get away from the upper Carnot efficiency - which in our atmosphere is right around 33% (a value we don't even come close to in practice).
The Ideal Gas Law, what a bitch!
This is a decent stop gap technology I suppose, but electricity is the way to go. Electric to mechanical energy efficiency approaching 85% (in practice!) Now if we can figure out how to minimize loss during transmission.... or how to generate the stuff ubquitously withut using a heat engine....
At that point it is the company's problem, not yours. In the absence of established policy you should ask for guidance before unilaterally destroying company property.
But then again you are on the way out, and it is highly unlikely that anyone will give a damn one way or the other as MIS is probably going to nuke your drive anyway.
Not really - companies have to be consistant in the way they treat (in this case terminate) employees.
From a legal stand point, it is safest to have a policy regarding all terminations as the same be it voluntary (I quit) or involuntary (firing or lay off).
Hell, if the guy simply slips and falls while on the premisis they are wide open for a lawsuit.
Best to decrease exposure to any potenital liability, give the guy his two weeks pay, and send him off.
This also protects the employee from any accustions of wrong doing during the transition, BTW.
Seems to me if you have to go to the bother of wiping your disk then you have something to hide aside from a few emails from the girlfriend/wife and some cookies from cnn.com.
This approach justifies such a policy from corporate. Everything on that drive is their property. Is some of it worthless to them? Probably. Delete that. However any unfinished code that is not checked in, fragments of designs, meeting notes, emails to colleagues - that is theirs and you have no business wiping it.
Do you really think they are going to recover deleted jpegs of your dog and various versions of your resume when you leave? Get over yourself!
...gave two weeks notice, came in the next morning and my workstation was gone.
Hopped on a lab machine... and my accounts were locked.
I was told to "document" my work. Aside from a description of what I was working on, and a rough sketch of my design (all of which was on some server and my workstations hard drive) I simply wrote "for further detail please refer to such and such files located on my corporate directory and workstation, to which I no longer have access." This ate up a day. I had to do this on a legal pad.
For 9 more business days I picked my nose and distracted my office mate.
Did I complain? Nope. I just made a mental note of how to give notice the next time:
1) Pick a time with a holiday preferably in the first week 2) Do it at the very end of the day Monday (that still counts as one day) 3) Make sure you have cleaned up after yourself on your machine and all accounts - well before the preceeding backup cycle (if there is one) 4) Pray to God you get the two weeks pay and shown to the door!
They speak English in Ireland, not to mention make less money than Americans... but that didn;t stop their jobs from fleeing to other countries now did it?
Have you ever spent time in mainframe environments? There are all kinds of "wacky" architectures to be found there.
My first job out of college was on a susyem with 3 CPU's. It was an MAI/B4 MPx8000 series mini. It had 9MB of RAM. Weirdly, the OS word size was 24 bits. Blocksize on the disk was 768 words.
The author is "sort of" right. THAAD was floundering badly in the 90's and was completely restructured in 1996. The battle management and sensors were fine, but the interceptor was a flop and completely redesigned.
He speaks of the old system, you of the new. The only thing in common between the two systems is the acronym, but even the first Word in it has changed.
Not to worry, the THAAD interceptor will probably be replaced with the SM-3 (the missile that the Aegis BMD system is based on). However the radars and C3BM will remain the same.
While I believe such a scenario is entirely possible, I think that our Pentium 4's and Sparc's are just not capable of enabling such a feat. The code to do so would either take several megabytes or be so strongly compressed that our machines simply would no be able to unpack it in under a decade.
It would sort of be like the NSA travelling back in time and trying to remotely root the Union Pacific's telegraph machines.
I have read (hey may as well start of with unsubstantiated factoids right off the bat!) that most estimates yeild results of "only" about 125 - 150 years worth of uranium at current consumption levels.
Could be be BS.
...atleast in my case.
I am a pretty decent coder, acoording to my bosses. Technical management can only take one so far. An IP lawyer who knows what he is doing should do pretty well (assuming I keep up with technology).
I would code until retirement, but it just doesn't seem realistic for a variety of reasons.
Capture the waste heat downstream from the converter (and place it close to the engine).
...some are better than others, some are cleaner than others, but we will never get away from the upper Carnot efficiency - which in our atmosphere is right around 33% (a value we don't even come close to in practice).
The Ideal Gas Law, what a bitch!
This is a decent stop gap technology I suppose, but electricity is the way to go. Electric to mechanical energy efficiency approaching 85% (in practice!) Now if we can figure out how to minimize loss during transmission.... or how to generate the stuff ubquitously withut using a heat engine....
...how's their trig?
They look weird.
Not really true: when you are laid off there generally is some sort of severance pay involved.
If you are fired... well tough you don't deserve any favors.
At that point it is the company's problem, not yours. In the absence of established policy you should ask for guidance before unilaterally destroying company property.
But then again you are on the way out, and it is highly unlikely that anyone will give a damn one way or the other as MIS is probably going to nuke your drive anyway.
Not really - companies have to be consistant in the way they treat (in this case terminate) employees.
From a legal stand point, it is safest to have a policy regarding all terminations as the same be it voluntary (I quit) or involuntary (firing or lay off).
Hell, if the guy simply slips and falls while on the premisis they are wide open for a lawsuit.
Best to decrease exposure to any potenital liability, give the guy his two weeks pay, and send him off.
This also protects the employee from any accustions of wrong doing during the transition, BTW.
Seems to me if you have to go to the bother of wiping your disk then you have something to hide aside from a few emails from the girlfriend/wife and some cookies from cnn.com.
This approach justifies such a policy from corporate. Everything on that drive is their property. Is some of it worthless to them? Probably. Delete that. However any unfinished code that is not checked in, fragments of designs, meeting notes, emails to colleagues - that is theirs and you have no business wiping it.
Do you really think they are going to recover deleted jpegs of your dog and various versions of your resume when you leave? Get over yourself!
...gave two weeks notice, came in the next morning and my workstation was gone.
Hopped on a lab machine... and my accounts were locked.
I was told to "document" my work. Aside from a description of what I was working on, and a rough sketch of my design (all of which was on some server and my workstations hard drive) I simply wrote "for further detail please refer to such and such files located on my corporate directory and workstation, to which I no longer have access." This ate up a day. I had to do this on a legal pad.
For 9 more business days I picked my nose and distracted my office mate.
Did I complain? Nope. I just made a mental note of how to give notice the next time:
1) Pick a time with a holiday preferably in the first week
2) Do it at the very end of the day Monday (that still counts as one day)
3) Make sure you have cleaned up after yourself on your machine and all accounts - well before the preceeding backup cycle (if there is one)
4) Pray to God you get the two weeks pay and shown to the door!
Will the BBC suffice?
s outh_asia/2002/india_pakistan/timeline/2001.stm
http://news.bbc.co.uk/hi/english/static/in_depth/
They speak English in Ireland, not to mention make less money than Americans... but that didn;t stop their jobs from fleeing to other countries now did it?
>> The only real problem that India has is with Pakistan...
Nice way to minimize coming within a cunt hair a nuclear war. Or does your memory not stretch back to 2000?
China already outsources some of its low end manufacturing to Vietnam citing lower labor costs.
We want Mars. Venus too.
Have you ever spent time in mainframe environments? There are all kinds of "wacky" architectures to be found there.
My first job out of college was on a susyem with 3 CPU's. It was an MAI/B4 MPx8000 series mini. It had 9MB of RAM. Weirdly, the OS word size was 24 bits. Blocksize on the disk was 768 words.
The author is "sort of" right. THAAD was floundering badly in the 90's and was completely restructured in 1996. The battle management and sensors were fine, but the interceptor was a flop and completely redesigned.
He speaks of the old system, you of the new. The only thing in common between the two systems is the acronym, but even the first Word in it has changed.
Not to worry, the THAAD interceptor will probably be replaced with the SM-3 (the missile that the Aegis BMD system is based on). However the radars and C3BM will remain the same.
Sort of... but the componants under test are sitting in a rack or on a bench - not in a complete assembly.
...to take over with such a signal.
While I believe such a scenario is entirely possible, I think that our Pentium 4's and Sparc's are just not capable of enabling such a feat. The code to do so would either take several megabytes or be so strongly compressed that our machines simply would no be able to unpack it in under a decade.
It would sort of be like the NSA travelling back in time and trying to remotely root the Union Pacific's telegraph machines.
It shows that a seed of technical sophistication is starting to take root in simple minds.
This is a double edged sword, but I suspect this is probably for the best.
If you are renting an apartment, you are not living like a king.
...I will laugh my ass off.
You install drivers you are unfamiliar with? If it doesn't come from M$ or from a hardware vendor, it isn't going on.
Uh, you too New Mexico!
(Somebody, probably European, is bound to think this is a serious post.)