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


Forgot your password?
Last Chance - Get 15% off sitewide on Slashdot Deals with coupon code "BLACKFRIDAY" (some exclusions apply)". ×

Comment Re:Important to note (Score 1) 421

So is weed. If they tested for weed at my last workplace, they'd have to have fired the whole the entire company, with the exception of some of the executives. They were more into coke. Microdosing LSD isn't really a big deal, although the strongest thing I take in the workplace is caffeine. I highly doubt anyone is going to rip off their clothes and proclaim their divinity on the doses we're talking about. Maybe if we had more women in the workplace this would be an interesting outcome...

Comment Re:Cost of access is key. (Score 4, Insightful) 345

however, we don't know the reasons the Polynesians expanded. It is highly doubtful a lone couple of polynesians set sail on the high seas to find new islands. The amount of provisioning and boat building required would indicate at least local levels of cooperation and contribution that would most likely be analogous to modern government sponsorship of exploration and colonization. These aren't the brave, rugged capitalist individualists you are looking for, either.

Comment Vague specs, changing requirements (Score 1) 491

Constant threat of being out-sourced, overseen by the same idiots who gave you shit all through high school, meant to feel worthless even though you just created products that will carry the company through the next 50 years, blah blah blah.

I mean, I'd just bury my depression in a tub of ice cream, but I guess some folks wanna kill themselves the easy way.

Comment Re:Everyone has to learn about it. (Score 1) 193

There's a new found disdain for DBAs, because they "slow things down" by pointing out issues before they become issues. Instead, every half-assed "web developer" also thinks they're a DBA because "web scale" or some bullshit. I've always found it ironic that businesses who depend upon the integrity of their data are the first to eschew the services of a good DBA because "slow" or because "nosql". Then again, I've generally always worked with competent DBAs would who ask questions about my queries and help me build new queries that followed better practices (as well as lightening the load on the db itself).

Comment Re:Where is there check? (Score 1) 366

This is exactly how we did it. I would call out my numbers one at a time, wait for confirmation (checking their copy), and continue. ", 1685" "check", etc. And yes, we would catch transposition errors t his way. Short-cutting this only saved less than a minute and the consequences were too "dire" to ignore. And then we'd do the same with fuel numbers, etc. Once our paperwork was double and triple checked, we'd sign off and hand to the crew to sign off on the numbers they needed to verify (fuel load, for example), they'd sign, and we'd be on our way. I always assumed the crew would also do a similar check with the numbers.

I really miss that job.

Comment Where is there check? (Score 3, Informative) 366

I used to be a Ramp Agent at a major international shipping firm. We did weight and balance for the flights. We had several layers of redundancy for our numbers: Every container number and weight was rechecked by another Ramp Agent, and then once again at the gate to match with the load sheets. We realized if we put the numbers in wrong, that could result in loss of life (not to mention aircraft assets and cargo). We took this job very seriously. Once we turned that paperwork (now done via ACARS, supposedly), I would hate to think that the cockpit just fat fingered the numbers in on their end without having a secondary check. "Hey Captain, can we check the numbers real quick?" Probably take them 15-30 seconds at most since they'd be concerned with big picture numbers and not individual positions.

Our informal mission is to improve the love life of operators worldwide. -- Peter Behrendt, president of Exabyte