Android News, Android Triks, Android Developer, and Android Viewers.

Sunday, May 31, 2015

Inside the Google[x] research lab: the best kind of failure factory

 
Google[x], your research lab at Mountain View faced with coming up with more "left-field" projects, is often a hotbed of broken boundaries, pushed limits and inventive thinking. These are the necessary ingredients for overcoming a number of the world’s biggest problems. Google[x] achieves these lofty goals, curiously, by seeking to accelerate failures.

Google[x], headed by Dr. Astro Teller, may be the group to blame for Google Glass, Project Loon, self-driving cars, smart for the purpose of and more. As Dr. Teller explains the unit’s function, Google[x] exists for the crossover between big problems, radical solutions and breakthrough technology.

Every project at Google[x] commences with a radical idea and hardly any idea how you can make it happen. Once a project continues to be settled on, the group goes about assessing its viability as fast as possible by getting against eachother into the world for real-time feedback. The only thing hindering the group’s efforts could be that the real world moves too slowly on their behalf.

In order to seek out out with the earliest possible opportunity make fish an idea is within the wrong path, they at Google[x] efforts to speed up the real-world to allow them to discover future failures before a lot of time or energy is poured into them. As Dr. Teller puts it: “it may be hard for the c's to find out a notion won’t work, but it’s safer to know now than after another year and a half.”

Dr. Teller comes with a humorous example. When Project Loon was centered on keeping its balloons airborne for 100 days, small punctures were causing problems. Because the tiny leaks were so small, it took weeks for your balloons to descend so they really could be inspected. So the group built a crack squad of leak detectors that aimed to analyze, isolate and remedy possible leak scenarios before they ever happened.

When the socks this device makers wore (no shoes allowed in balloon production) were suspected for creating skin pores in the balloons before they ever left the bottom, Google[x] had them perform a complete line dance on the balloon because of their regular socks and then with a fresh balloon with extra-fluffy socks. Not surprisingly, there are fewer leaks. This is how the full team works: identify failures by whatever means necessary by increasing the real-world to get things about the right path as soon as possible.

While starting off to find problems may seem disenchanting, the projects that reveal diminishing weaknesses, or simply just generate better solutions, are those that develop. Take Google’s self-driving car project, as an example.


After handling freeways successfully, Teller attempted to get real visitors to be the "co-drivers": stepping in mere when necessary. But, being people, they got lazy, so Google[x] made the seemingly crazy decision to generate the cars fully autonomous.

Then, after driving countless miles without incident, the actual was deemed too boring, producing no useful data. So, instead of wait for that rare, random occurrences to happen, Google[x] built another team to quite literally hurl every form of vehicular and pedestrian weirdness for the cars.

The success with the project is clear from the recent announcement that self-driving cars will be within the roads in Mountain View later come early july. As Dr. Teller puts it: “Half on the hard work is determining what the real-world is attempting to tell you.” Once you know what that may be, the fun work begins of fabricating those viable moonshots on the planet.

Inside the Google[x] research lab: the best kind of failure factory Rating: 4.5 Diposkan Oleh: Unknown

TrimaKasih telah berkunjung di Tips-Android.Com

Silahkan komentar nya untuk Artikel di atas
Semoga bermanfaat. Out Of Topic Show Konversi KodeHide Konversi Kode Show EmoticonHide Emoticon

Terima kasih sudah berkomentar