Never pick a fight with someone crazier then you. Instead of fighting, ignore them and put all that time and energy into volunteering for Habitat For Humanity or something similar. Then again, you could take a lesson from the Middle East and blow up a school bus full of children in protest.
I always thought that all those Xbox 360s and PS3s would make a great cloud when they are not being used. One could for example trade idle time for Xbox Live points to make it worthwhile. I would think Sony could cut a similar deal and render their movies on all of the idle PS3s.
The chance/skill ratio in chess is 0, because there's no chance in chess. I don't understand how you can say that.
There are some elements of chance in chess since players are better prepared for some openings then others. All grandmasters have some novel lines they have developed that they are ready to spring upon their opponent if given the chance and the game is critical enough to reveal it. Since they are on the clock, there is not much time to ponder a response to something that has been worked out over months or years.
Where I once worked, we handled human blood and were required to wipe everything down using a bleach spray. This may be too harsh for your computer or at least the screen, but it is effective.
Don't people ever learn. If you don't install a firewall, anti-virus protection, and anti-spyware software on your coffee maker, you deserve to be hacked. My coffee maker runs Linux and has never been hacked.
One needs an odd number of monitoring systems, so two will not suffice. If there is only two and they both report two different things then one still has to shut down the plant until things are sorted out. In fact, now that there is two systems, there is twice the chance of something going wrong. If there are three systems then the majority wins. There is still the problem of what to do with the bad system as hot swapping a new one in has the potential to bring everything down. It would also be a nightmare to test all the failure conditions. For example, one of the early shuttle launches was scrubbed because when all the redundant computers tried to synch up, the clock signals edge appeared and it had only been designed to deal with the high and low states of the signal and all the testing never encountered this condition. Redundant systems can also give a false sense of security if they are not maintained independently. For instance, if someone makes the same mistake to all of them or a batch of defective parts is used on all of them then they can easily all fail for the same reason within a short timespan of each other.
"GROSS NEGLIGENCE - Failure to use even the slightest amount of care in a way that shows Recklessness or willful disregard for the safety of others." - 'Lectric Law Library.
Yeah, those bastards, the way they used THE SLIGHTEST AMOUNT OF CARE in designing a system that shuts down in response to unexpected data so as to avoid RECKLESSNESS with the SAFETY OF OTHERS. And to top it off they had the gall to report it instead of covering it up.
"Notarized" signatures are supposed to be more secure, though if you can produce a convincing fake ID, they probably aren't. In my experience, the notary usually requires a fingerprint as well as a signature which helps in tracking the person down and prosecuting them.
And when it comes to partying, the only special way I can think of that mathematicians like to party is hard. I used to party with a bunch of Swiss Post-Doc chemists and they really partied. The weird thing is they all were named Andreas.
See who can recite Pi the furthest in Hexadecimal (3.243F6A8885A308D31319...)
Play pin the tail on the integer?
Dress up as your favorite nonlinear equation.
Start a drinking game where everyone increases their drinks parabolically. (or alternatively: everyone drinks when someone says "Archimedes.")
TP the English department utilizing the golden spiral....
Sounds like my last math party. We played pin the tail on the infinite series Watched American PI Had a drinking game where everyone had to drink if there was an awkward pause in the conversation Played spin the bottle. Not so much fun though as there weren't any girls. There was a heated argument about the best Doctor Who but luckily no fights broke out because everyone was wearing glasses Someone told a hilarious joke about a frayed knot A bunch of people competed to see who could solve the Rubiks's cube the fastest Someone brought a great Lori Anderson compilation CD.
Boundary conditions are nice but first you need to at least make sure that each line of code is executed first. I once read about a program that ran for years without a problem and then after many years a line of code finally was executed and the process crashed. Before getting fancy in testing, one should first weed out simple blunders and to do that, one needs to make sure each line of code actually runs. The same holds true for a GUI, every button / menu item needs to be executed. When the end user clicks on something and the program crashes, the product loses a lot of credibility quality wise no matter how many boundary conditions or code paths are tested. After getting this far, one can then start testing boundary conditions. One also needs to test each use case including the failure modes but once again all the very simple use case success scenarios need to be tested since the user will think that if one can't get the simple things correct then things are going to get a lot worse. Use cases also help protect the schedule, as defects will continuously be found and fixed instead of having a big bang at the end. One of the most important aspects of writing use cases, is the questions they generate such as 'What happens if...?', 'Is null treated the same as an empty String?', 'Does case matter?', 'Why does it take so long?', 'Why does this work on Windows but not UN*X'?', and the very important, 'I made some changes did I break anything?'.
Slashdot Mirror
Ellison did buy nCUBE so he does have some hardware experience albeit a not very positive one.
But they could do like they did with Rolm and transfer all their dead end managers to it and then sell it.
Never pick a fight with someone crazier then you. Instead of fighting, ignore them and put all that time and energy into volunteering for Habitat For Humanity or something similar. Then again, you could take a lesson from the Middle East and blow up a school bus full of children in protest.
I always thought that all those Xbox 360s and PS3s would make a great cloud when they are not being used. One could for example trade idle time for Xbox Live points to make it worthwhile. I would think Sony could cut a similar deal and render their movies on all of the idle PS3s.
June 2, 2009, 9:16 p.m. EDT: Third missile enters Earth's atmosphere and detonates. Earth begins nuclear winter.
August 3, 2009, 3:24 p.m. EDT: Al Gore makes a movie about the coming ice age and wins a second Noble Prize.
The chance/skill ratio in chess is 0, because there's no chance in chess. I don't understand how you can say that.
There are some elements of chance in chess since players are better prepared for some openings then others. All grandmasters have some novel lines they have developed that they are ready to spring upon their opponent if given the chance and the game is critical enough to reveal it. Since they are on the clock, there is not much time to ponder a response to something that has been worked out over months or years.
Where I once worked, we handled human blood and were required to wipe everything down using a bleach spray. This may be too harsh for your computer or at least the screen, but it is effective.
Remember that scientists are naturally skeptical. To claim something is exactly 1KG takes balls.
What would you buy him as a retirement gift?
A solid gold house and a rocket car.
Don't people ever learn. If you don't install a firewall, anti-virus protection, and anti-spyware software on your coffee maker, you deserve to be hacked. My coffee maker runs Linux and has never been hacked.
I've been praying this would happen.
One needs an odd number of monitoring systems, so two will not suffice. If there is only two and they both report two different things then one still has to shut down the plant until things are sorted out. In fact, now that there is two systems, there is twice the chance of something going wrong. If there are three systems then the majority wins. There is still the problem of what to do with the bad system as hot swapping a new one in has the potential to bring everything down. It would also be a nightmare to test all the failure conditions. For example, one of the early shuttle launches was scrubbed because when all the redundant computers tried to synch up, the clock signals edge appeared and it had only been designed to deal with the high and low states of the signal and all the testing never encountered this condition. Redundant systems can also give a false sense of security if they are not maintained independently. For instance, if someone makes the same mistake to all of them or a batch of defective parts is used on all of them then they can easily all fail for the same reason within a short timespan of each other.
Yeah, those bastards, the way they used THE SLIGHTEST AMOUNT OF CARE in designing a system that shuts down in response to unexpected data so as to avoid RECKLESSNESS with the SAFETY OF OTHERS. And to top it off they had the gall to report it instead of covering it up.
Are they going to have force feedback?
So how many licks does it take to get to the center?
Does this mean that scented ring tones will be next? I guess instead of vibrate we can just set the phone to silent but deadly.
(3.243F6A8885A308D31319...)
Play pin the tail on the integer?
Dress up as your favorite nonlinear equation.
Start a drinking game where everyone increases their drinks parabolically. (or alternatively: everyone drinks when someone says "Archimedes.")
Sounds like my last math party.TP the English department utilizing the golden spiral....
We played pin the tail on the infinite series
Watched American PI
Had a drinking game where everyone had to drink if there was an awkward pause in the conversation
Played spin the bottle. Not so much fun though as there weren't any girls.
There was a heated argument about the best Doctor Who but luckily no fights broke out because everyone was wearing glasses
Someone told a hilarious joke about a frayed knot
A bunch of people competed to see who could solve the Rubiks's cube the fastest
Someone brought a great Lori Anderson compilation CD.
...Being yourself and getting the girl are just not going to happen if your life mainly consists of sitting in your basement playing video games.
That's whey I spend all my time memorizing train schedules.
Boundary conditions are nice but first you need to at least make sure that each line of code is executed first. I once read about a program that ran for years without a problem and then after many years a line of code finally was executed and the process crashed. Before getting fancy in testing, one should first weed out simple blunders and to do that, one needs to make sure each line of code actually runs. The same holds true for a GUI, every button / menu item needs to be executed. When the end user clicks on something and the program crashes, the product loses a lot of credibility quality wise no matter how many boundary conditions or code paths are tested. After getting this far, one can then start testing boundary conditions. One also needs to test each use case including the failure modes but once again all the very simple use case success scenarios need to be tested since the user will think that if one can't get the simple things correct then things are going to get a lot worse. ...?', 'Is null treated the same as an empty String?', 'Does case matter?', 'Why does it take so long?', 'Why does this work on Windows but not UN*X'?', and the very important, 'I made some changes did I break anything?'.
Use cases also help protect the schedule, as defects will continuously be found and fixed instead of having a big bang at the end. One of the most important aspects of writing use cases, is the questions they generate such as 'What happens if
Thats's funny because my professor in college said all OS's will be written in assembly in the foreseeable future.
The Soviets did that with their nuclear submarines. The designers of the reactors had to ride on the maiden voyages.
Moxi has a jump back feature. They may have licensed it from Tivo though.