Recently in Technology Category
Pat Delany's open-source designs for human-powered machine tools that can be built with inexpensive scrap for about $200. The Multimachine, built out of an auto engine block, serves as a grinder, mill, lathe, and saw. The 16" swing screw-cutting lathe is made of concrete and scrap steel, using techniques that date back to World War I. A hand-powered drill can be built with scrap wood and parts for $1. A treadle-powered generator uses a car's alternator to turn human power into electricity that can charge batteries and mobile phones. (A commenter suggests "a flywheel on the bottom horizontal shaft, at the opposite end of the shaft to the large driving wheel. Firstly, this would stop the frame from toppling over if the ground was uneven. Secondly, once the mechanism was up to speed, the effort required would be much less than the initial start-up; it would simply be a case of keeping the flywheel up to speed.")
Delany and his open-source designs are featured in the latest issue of Makezine. opensourcemachinetools.org has even more information on these projects and historical do-it-yourself machine building.
MORE: The Open Source Machine site also has how-to articles for building an air compressor, hydraulic press, and screw press, for blacksmithing, and farm shop work from the early 20th century and U. S. Army courses on drafting, welding, machine tools, lathes, milling machines, and band saws.
You can follow Pat Delany on Twitter.
Resuscitation science has advanced tremendously, but the key techniques to bringing someone back from cardiac arrest aren't as widely known and used as they should be, says the author of Erasing Death. Chest compressions, no more than 8 breaths a minute with an ambu bag, cooling the body (down to about 32 degrees Celsius, or about 90 degrees Fahrenheit). "We use pads that get attached to the thighs and the upper body. In a matter of hours, the cooling machine brings the body temperature down to the desired level. But you could also do this at home, if you found someone there in cardiac arrest. Call an ambulance, administer CPR and place a bag of frozen peas or other frozen vegetables on the patient. It helps to protect the brain....
"Most brain damage after resuscitation occurs not within the first few minutes of death, but in the hours up to the first 72 hours after resuscitation. But with proper post resuscitation care, we can minimize that.... A recent study found that the optimal length of resuscitation to yield higher survival is at least 40 minutes. Yet most doctors will stop within 20 minutes.... As long as hospitals don't require their resuscitation doctors to implement all the nuances required to save brains and lives after cardiac arrest through fully trained specialists, survival rates in general will not improve."
Read through to page 2 to learn about Parnia's research into near-death experiences.
Why you want a hot skillet, how to tell when it's ready to turn over, and why too crowded a pan will result in "grayed" meat instead of properly browned meat.
Very cool and inexpensive hack
A handsome infographic showing layouts and image sizes on Twitter, Facebook, Pinterest, YouTube, LinkedIn, Google+, and Instagram.
"If you simply use the CrashPlan software without a CrashPlan account you can backup your data to a secondary drive on your computer, another computer on your home network, and to your friend's/brother's/mom's computer all for free--don't worry the data is encrypted via the Blowfish algorithm. Want to add cloud-based storage into that? You can backup 2-10 computers for a mere $10 a month with unlimited storage--it's an outrageous bargain compared to other cloud-based storage solutions."
"The primary principle of backing up your data is that any important data should exist in two or more physical locations at once. You cannot create a backup and delete the original, or else it is no longer really a backup."
"First off, there are, I believe, really two reasons why we're so bad at making estimates. The first is the sort of irreducible one: writing software involves figuring out something in such incredibly precise detail that you can tell a computer how to do it. And the problem is that, hidden in the parts you don't fully understand when you start, there are often these problems that will explode and just utterly screw you.
"And this is genuinely irreducible. If you do "fully understand" something, you've got a library or existing piece of software that does that thing, and you're not writing anything. Otherwise, there is uncertainty, and it will often blow up. And those blow ups can take anywhere from one day to one year to beyond the heat death of the universe to resolve....
"The key is that you first accept that making accurate long-term estimates is fundamentally impossible. Once you've done that, you can tackle a challenge which, though extremely difficult, can be met: how you can your dev team generate a ton of value, even though you can not make meaningful long-term estimates?"