Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!


Forgot your password?
DEAL: For $25 - Add A Second Phone Number To Your Smartphone for life! Use promo code SLASHDOT25. Also, Slashdot's Facebook page has a chat bot now. Message it for stories and more. Check out the new SourceForge HTML5 Internet speed test! ×

Submission + - Low-Tech Way To Counter Drones

evil_aaronm writes: With the advent of government drones flying 24x7 over this "Land of the Free," what are some relatively low-tech counter-offensive methods for diminishing a drone's spying effectiveness, or taking it out altogether?

Hypothetically, of course: I'd never actually suggest that upstanding, law-abiding citizens impede the government in any manner, shape or form.

Submission + - Consequences of Non-Action 2

evil_aaronm writes: I work for a large international company producing systems for health care, specifically medical diagnostics. This is a product upon which lives depend: our systems can cause great joy when people learn that they do not have "dreaded disease", or death, if our results are incorrect and treatment is delayed. I greatly enjoy working on this product, but I can't stand my manager: our definitions of "quality" are vastly different. The code we produce could supply more than a year's worth of Daily WTF fodder. Every time I try to improve our code, I'm shot down because this manager can't handle abstract concepts, among other things. An example, with no embellishing, and one of many: instead of writing a loop to process, say, 10 files the exact same way, he wants to cut-and-paste 10 blocks with the name of the file changed in each block. My equivalent loop was rejected: too complex. Partly because of this, after two-plus years, I'm changing departments and will no longer have to work with him, for which I'm grateful. My question is: How do I — or do I at all — warn management or, more importantly to me, our customers, that this product is a festering pile of shit that's waiting for the smallest provocation to cause said shit to spew all over? I almost believe upper management doesn't want to know: Head in Sand syndrome. That doesn't mitigate my responsibility to make it known to -someone- that this product is a large defect waiting to happen. Changing groups also doesn't relieve my sense of concern that someone could very well die because I did nothing to fix this.

Submission + - What to do with old tech books? 2

evil_aaronm writes: Over the years, starting in the late 80's, I've collected a lot of technical books. Now, aside from one or two timeless classics, the vast majority of them are gathering dust. I'm sure I'm not the only one in this predicament, but how do I get rid of these gems? Giving them away, selling them, I don't care, really.

Slashdot Top Deals

It is masked but always present. I don't know who built to it. It came before the first kernel.