Mass Fatality Identification System
Shipud writes "
Bio-IT World is running a
story on how Gene Codes corporation created the Mass Fatality Identification System (M-FISys) in the aftermath of the 9/11 attacks. The story goes into the details of processing large amounts of data, aiming for a 99.9% accuracy rate, and
extreme programing."
extreme programing
One of the philosophies of extreme programming is "once and only once". Glad to see you applying this philosophy to that redundant "M"! Down with unnecessary repetition!
In the even of identification will be done in the following manner: The 30 of us that survive, that aren't cockroaches, please raise your hands.
Often in Error, Never in Doubt.
Mass fatality system! Oh boy! All of my many nefarious plans will see fruition, I just hope it's open source. Oh, it's an Identification system? Slot off /.!
Let's see..
... check. ... check. ... check.
:)
new technology
mass fatatilies
extreme programming
Yep, Slashdotters will love this one.
In a clone infested future this will be useless
My communication skills have improved drastically.
Sadly, not to the point of using paragraphs.
pretty much identify it as a mass fatality? I'd think that would at least be a major clue.
."
Or are we going to start giving them names, like hurricanes?
"In mass fatality "Jane" today. .
What am I missing?
KFG
Markup languages are hardly extreme, but surely they could push the bounds of the latest standards and do something truely extreme. ;-)
Mike
I'll look at it, but I can imagine myself just pissing off my programming partner by inserting characters right where her cursor is until she smashes the backspace key... on my head.
http://pcblues.com - Digits and Wood
There is also a 'ramming' in programming, but I got nothin' for that.
haha - even the moderation is funny - flamebait! hahahahahaha
"Otherwise, you run the danger of looking at the code later, and not being in that mental ecstacy of understanding everything at once"...
okay, someone has to stop coding while on LSD...
"conceived of a frightfully, inhumanly efficient and clever way of doing something that no human may ever imagine again."
Okay, and I imagine this happens to you, how many times a day? Month? Year? Lifetime? And of those times, what percentage of the time do you look back and wonder what the hell you were smoking? Or worse yet, have to come back to your "clever code" and modify it? Perhaps having someone else there to provide sanity checks might help?
Unless it's a solo poject for pure comp-sci research (and even then you're going to have to write a paper on it), your code doesn't exist in a vacuum. Whatever "clever" code you make will be a headache to whomever has to come afterwards to change, modify, or maintain it. Especially if it's "something that no human may ever imagine again."
Do tell me more about how carbon unit pairings lead to friction. I sense a fascinating analogy.