Construction with Quadrotor Teams

What people said

0x8BADF00D · 2018-08 · Reference

Some construction jobs are better than others. In SF, for example, there are many undersea construction jobs that pay very well. The CTO of Coinbase envisions that construction[0] as an industry is ripe for disruption, reaping the fruits of technology like VR controllable drones[1]. If you make construction like a video game, “young people” will flock to it. [0] [LINK] [1] [VIDEO]

Read the original HN comment ↗

reustle · 2015-07 · Reference

This format is painful to read, so I'm copying the content here. This is a series of tweets by [LINK] -- If you are using software to go after a legacy physical vertical, we are most excited if you do it "full stack" [0]. With @counsyl, we found that one cannot live by bioinformatics alone. So built a full clinical lab + software + national salesforce. Here is a video of our robotic genome factory: Also: insurance coverage, clearances, clinical integration... [1] The reason to do full stack is that it's hard to replace just one layer of an outdated legacy stack. CAC & integration costs can kill. For example, consider "restaurant powered by technology" vs "tech for restaurants". With code, reinvent industry and make better margins. You cannot automate something till you've done it manually many times. You cannot abstract an API till you've seen many specific examples. Need to build a site of the scale of [LINK] - and encounter all the problems - before you could do [LINK] . Reinventing agriculture? Build new kind of farm, w/ solar panels & self-driving tractors. Control all factors, show that code cuts costs. More examples of full stack startups.. Education: [2], Autos: [3], Hospitality: [4] By doing it end-to-end, you see things. First, sometimes a good reason beyond tradition (eg regulatory, logistical) for legacy practices. Second, your control of adjacent layers may eliminate the initial problem you were trying to solve. Analogous to: [5] Third, solving whole problem build

Read the original HN comment ↗

andrewcooke · 2011-01 · Reference

Actually, you may be more right than you know (sorry). I've found this quote: "We tell the quadrotors what structure to build and they figure out the assembly plan and then build it." [VIDEO] It still doesn't look very swarm-like to me (more like some kind of planner algorithm; I know the quote implies a distributed intelligence, but look at the way they queue always in exactly the same place, do laps, etc etc), but that certainly sounds more promising.

Read the original HN comment ↗