I disagree.... It begins much earlier than that. For me, it started with Lego and Erector sets.
Development is my adult version of Lego. The main difference being that with Lego, you must to plan for the pieces you have - with development - you just make the pieces you don't have.
It's convenient to put a black-and-white low-res placeholder image on a page using a data uri, so the area of the page where the full-resolution image will eventually be placed isn't blank while waiting for the much larger image to download.
As Shor's algorithm is only supposed to give the correct answer 50% of the time, this is a good result.
How is it useful to have the correct answer 50% of the time? When designing computing algorithms, wouldn't you want it to return the correct answer 100% of the time?
I would further enhance the question by asking: What the hell are you collecting that each sensor stores 500GB in 24 hours - photos? Seriously, these aren't sensors - they're drive fillers.
Seriously, if "sensor units scattered across a couple square miles" means 10 sensors - that's 5 Terabytes to initialize and mount in 30 seconds. I suspect that the number is greater than 10 sensors because the rest of the requirements are so ridiculous.
And why the sneakernet? If they're in only a couple of square miles - why not set up a mesh network and deliver real-time data without the need for daily collection? 30 seconds to boot probably wouldn't be a requirement if the system is only booted once.
All of the questions about why this person is even involved are probably moot. He'll be outed as an idiot in short order.
My current Thinkpad is a Z61M also - I was initially concerned about it's lifespan until I upgraded it to a 64bit processor. The memory still bothers me though - why they put a bios capable of recognizing 4GB with a chipset capable of addressing only 3GB is beyond me...
I'm not even considering anything other than a thinkpad. Since the z61m was still an IBM creation, I have yet to have a Lenovo experience. Hopefully Lenovo is holding the same high standard.
With directional antennas and amplifiers, I've set up a stable 802.11b connection at 17 miles. I remember reading that Cisco had one going between mountaintops at 50 miles. All of this was 5 years ago, so things are probably more impressive today.
When drive bearings begin to fail (when you can hear it whine or groan), the freezer method is what I use.
I have recovered data from 5 drives this way.
The problem with freezing is moisture. Any moisture in the drive can freeze onto the platters or heads causing physical damage when the drive spins up. I've seen a video telling users to never freeze their drives, and they show the internals of a drive covered in frost. I'm convinced they rigged the drive to do this so they could boost their own data recovery business.
My method is to wrap the drive in paper towels while it's warm. Two or three layers will do. Then, take the warm/wrapped drive and put it into a zip-lock bag. Use a straw to pull out the air - you don't need a vacuum seal or negative pressure - just remove as much air as you can. Then put the drive in the freezer for several hours.
While it's cooling off, make a list of the data you want to retrieve in order of importance. The freezer method might not work a second time - so it's important to get the most valuable data first. Prepare your recovery system - use a USB adapter to connect the drive to an already running system. Don't try to insert your frozen drive into your computer and boot from it - you will be wasting valuable time.
When the drive is nice and cold - attach it to your computer and immediately begin to recover your data. Don't waste time - you might only get one shot at it.
5 times I've done this - mostly for customers - once for my own laptop drive.
There is a silver lining. Open source projects like Chromium and Firefox are agile enough to support recent snapshots, while Microsoft will have trouble keeping up - and will, in all likelihood, be years behind the times.
This might be the final nail in the IE coffin - driven one snapshot at a time.
I tried some of those "hacks" to get X-Code 4.3 to run on Snow Leopard, but it didn't work and I had a deadline. I gave it a day of trying hacks before I I went to get a mac that was "compatible" with 4.3.
If they make the next version of X-Code support only Mountain Lion like they made the current version only support Lion - I'm going to scream! Because my clients wanted to support features of the latest iOS, I had to upgrade to a new Mac because my older model couldn't run Lion - which is required for the latest X-Code.
Slashdot Mirror
I disagree.... It begins much earlier than that. For me, it started with Lego and Erector sets.
Development is my adult version of Lego. The main difference being that with Lego, you must to plan for the pieces you have - with development - you just make the pieces you don't have.
Of course, I still play with Lego.
THANK YOU!
there will be a disaster in 2012
It's convenient to put a black-and-white low-res placeholder image on a page using a data uri, so the area of the page where the full-resolution image will eventually be placed isn't blank while waiting for the much larger image to download.
This would have been ok:
<joke target="for the impaired"/>
From your description, I think your friend suffers less from any handedness issue - and more from the 10% rule.
http://www.urbandictionary.com/define.php?term=Ten%20Percent%20Rule
You must be 10% smarter than the equipment you are trying to operate.
I saw it.
I'm satisfied with that answer.
Not really, but I did get a good chuckle...
From TFA:
As Shor's algorithm is only supposed to give the correct answer 50% of the time, this is a good result.
How is it useful to have the correct answer 50% of the time? When designing computing algorithms, wouldn't you want it to return the correct answer 100% of the time?
I would further enhance the question by asking: What the hell are you collecting that each sensor stores 500GB in 24 hours - photos? Seriously, these aren't sensors - they're drive fillers.
Seriously, if "sensor units scattered across a couple square miles" means 10 sensors - that's 5 Terabytes to initialize and mount in 30 seconds. I suspect that the number is greater than 10 sensors because the rest of the requirements are so ridiculous.
And why the sneakernet? If they're in only a couple of square miles - why not set up a mesh network and deliver real-time data without the need for daily collection? 30 seconds to boot probably wouldn't be a requirement if the system is only booted once.
All of the questions about why this person is even involved are probably moot. He'll be outed as an idiot in short order.
Newsflash, the Dyson Air Multiplier has blades.... they're hidden in the base.
http://electronics.howstuffworks.com/gadgets/home/dyson-bladeless-fan1.htm
Yup, after a little research - I found a processor upgrade was possible. So I searched ebay and found one. This is the title of the auction I won:
Intel T7200 Core 2 Duo 2.0 Ghz laptop processor 4 MB L2 Cache
Posting from my now 64bit z61m now
My current Thinkpad is a Z61M also - I was initially concerned about it's lifespan until I upgraded it to a 64bit processor. The memory still bothers me though - why they put a bios capable of recognizing 4GB with a chipset capable of addressing only 3GB is beyond me...
I'm not even considering anything other than a thinkpad. Since the z61m was still an IBM creation, I have yet to have a Lenovo experience. Hopefully Lenovo is holding the same high standard.
The day I bought my first thinkpad was the day I stopped replacing broken laptops.
But it will probably last twice as long....
With directional antennas and amplifiers, I've set up a stable 802.11b connection at 17 miles. I remember reading that Cisco had one going between mountaintops at 50 miles. All of this was 5 years ago, so things are probably more impressive today.
We know that he didn't weigh the same as a duck - those people were burned.
When drive bearings begin to fail (when you can hear it whine or groan), the freezer method is what I use.
I have recovered data from 5 drives this way.
The problem with freezing is moisture. Any moisture in the drive can freeze onto the platters or heads causing physical damage when the drive spins up. I've seen a video telling users to never freeze their drives, and they show the internals of a drive covered in frost. I'm convinced they rigged the drive to do this so they could boost their own data recovery business.
My method is to wrap the drive in paper towels while it's warm. Two or three layers will do. Then, take the warm/wrapped drive and put it into a zip-lock bag. Use a straw to pull out the air - you don't need a vacuum seal or negative pressure - just remove as much air as you can. Then put the drive in the freezer for several hours.
While it's cooling off, make a list of the data you want to retrieve in order of importance. The freezer method might not work a second time - so it's important to get the most valuable data first. Prepare your recovery system - use a USB adapter to connect the drive to an already running system. Don't try to insert your frozen drive into your computer and boot from it - you will be wasting valuable time.
When the drive is nice and cold - attach it to your computer and immediately begin to recover your data. Don't waste time - you might only get one shot at it.
5 times I've done this - mostly for customers - once for my own laptop drive.
There is a silver lining. Open source projects like Chromium and Firefox are agile enough to support recent snapshots, while Microsoft will have trouble keeping up - and will, in all likelihood, be years behind the times.
This might be the final nail in the IE coffin - driven one snapshot at a time.
I tried some of those "hacks" to get X-Code 4.3 to run on Snow Leopard, but it didn't work and I had a deadline. I gave it a day of trying hacks before I I went to get a mac that was "compatible" with 4.3.
Holy upgrades Batman!
If they make the next version of X-Code support only Mountain Lion like they made the current version only support Lion - I'm going to scream! Because my clients wanted to support features of the latest iOS, I had to upgrade to a new Mac because my older model couldn't run Lion - which is required for the latest X-Code.
It took 5 years for the first malware to show up.
Wrong! It took 5 years for the first malware to be identified and publicly acknowledged.
How many more exist secretly, awaiting a clever analyst?
maybe you should read it again
http://php.net/manual/en/function.number-format.php
it says
Return Values
A formatted version of number.
PHP is well documented. in another reply, I provided a link to the number_format function.
it expects a float, not a null or a string. the documentation is very clear.
Garbage in - Garbage out
If you provide a string or null to a function that expects a float - what do you expect it to return - a unicorn barfing a rainbow?
If you don't want to initialize the input - fine! It's easy enough to do it with a conditional within the function itself!
$input=null; // $output = "0";
$output = number_format((is_numeric($input)?$input:0),0);