Tag Archive for: tiny

DARPA laser research boosts airborne death rays, tiny laser scanners

This week has been laser week at the Defense Advanced Research Projects Agency, with two very different laser-based programs hitting major milestones: an inexpensive array of lasers on a single chip that can be used as sensors on drones and robots and a killer laser system that could blow up missiles, shells, and possibly vehicles and people.

Yesterday, DARPA announced the successful test of a single-chip laser detection and ranging system that makes it possible to build inexpensive, lightweight short-range “phased array” LADAR that could be mounted on small unmanned aircraft, robots, and vehicles. The technology could bring low-cost, solid-state, high-resolution 3D scanning to a host of devices in the near future.

Called SWEEPER (Short-range Wide-field-of-view Extremely agile Electronically steered Photonic EmitteR), the sensor technology embeds thousands of laser-emitting dots microns apart on a silicon chip—creating a “phased array” optical scanning system that can scan rapidly across a 51-degree arc without the need for mechanical rotation. In the latest test, the system was able to scan back and forth across that entire arc more than 100,000 times per second.

Read 5 remaining paragraphs | Comments


Ars Technica » Technology Lab

The Tiny Model Town Where the Military Trains for Cyber Warfare – Gizmodo


Gizmodo

The Tiny Model Town Where the Military Trains for Cyber Warfare
Gizmodo
In an undisclosed location in New Jersey, there's a tiny little town that's used as a training grounds to prepare the military for cyber warfare. No, tinier than that. Think more like model train sized. It's called CyberCity, and WNYC's New Tech City

and more »

cyber warfare – read more

What are best practices for reusing tiny snippets of code across projects?

Stack Exchange

This Q&A is part of a weekly series of posts highlighting common questions encountered by technophiles and answered by users at Stack Exchange, a free, community-powered network of 100+ Q&A sites.

Stack Exchange user and C# developer George Powell tries hard to follow the DRY principle. But as any good dev knows, it’s not always possible, or even optimal, to stay original. Powell writes:

Often I write small methods (maybe 10 to 15 lines of code) that need to be reused across two projects that can’t reference each other. The method might be something to do with networking / strings / MVVM etc. and is a generally useful method not specific to the project it originally sits in.

So how should you track shared snippits across projects so you know where your canonical code resides and know where it’s in production when a bug needs to be fixed?

Read 15 remaining paragraphs | Comments


Ars Technica » Technology Lab