A public agency that uses an unmanned aircraft system, or contracts for the use of an unmanned aircraft system, pursuant to this title shall first provide reasonable notice to the public. Reasonable notice shall, at a minimum, consist of a one-time announcement regarding the agency’s intent to deploy unmanned aircraft system technology and a description of the technology’s capabilities.
There's also some reasonable limitations on data captured by drones (can't be kept long) and a requirement to log who requests drone missions. If only there was some federal body that could come up with some reasonable standard for all states...
Those of us with 6-digit IDs remember.
What I want to know is this: when did we 6-digit ID folks become the Lawn Guardians? Will no one think of the 4-digit'ers?!
I mean seriously, why would you want Mojang?
Maybe they don't want to buy it, they just want to leak a salacious story on the day some other company had big news?
...now my basement looks like something out of The Matrix.
You're farming humans for power?
Isn't that why we have kids?
I assume you missed the part about building 10 single-room buildings in a day for $5,000 each.
Well, the price is right, but people have been building modularly for a long time. Single room buildings don't really seem that challenging, especially since it is just a concrete box.
The Hilton Palacio Hotel in San Antonio was built in just 202 days, and that was 500 rooms, fully furnished, decorated and kitted (down to the bottle openers and coffee makers). And this was back in 1968.
I can't remember the last time a [major] web site or web framework was done in Perl.
Oh, I dunno, how about booking.com (about)? 'World's leading online accommodation provider' where 650K rooms a night are booked (they're owned by Priceline group, if that's a more popular brand where you live)?
A YAPC talk by one of their employees says 99% of their code is Perl. Check out their dev blog.
workstations inside the plasma conduits of the main weapon
Management considers this a "feature".
I was just going to write the same thing: if you hired someone you trust, trust that they are going to do the job well.
I like the three month transition plan given by Capt.DrumkenBum below, but I'd also like to add that you should try not to take too much pride or ownership in your existing systems. If new guy is going to change them and has good reason, be supportive, even if it feels personal. New guy has to run the ship now, let him run it the way it works, and works for him. Even if you have to say goodbye to one of your own creations and ways of doing things.
Having been there myself, it isn't always easy to go from micro to macro (or trusting someone else to handle some your old micro), but try to think of it is standing on shoulders instead of standing on toes. Now you have bigger challenges to face.
I'm sure there's a John Travlota joke about letting go to be made here...
Williams F1 has been working on this technology for quite awhile now. It's definitely fascinating. This video shows the technology applications.
Porsche also used the same Williams tech for their endurance 911 GT3R.
Nothing really new to see here; another instance of racing tech trickling down to production vehicles.
The biggest difference between time and space is that you can't reuse time. -- Merrick Furst