I actually was taught DRAKON charts (a variation of it) in high school back in '96. It tremendously helped me in more ways than strictly programming (which I never embraced). My teacher used to call it pseudocode back then, although Pseudocode is different. At the time, generating a high level overview of the processes in DRAKON before building any code was mandatory, and it sped up code generation because you always knew what the next steps would be.
Last time I checked (last week), 1TB worth of empty BDRs is about twice more expensive than a 2 TB HDD. it's better to buy 2x 1 TB drive, back-up with redundancy and keep them plugged in but powered off, or store them in two different locations.
Very simplistic analogy: You rip a sheet of paper, it makes noise. Once you finished with it, no noise would ever come out of it, but someone in the distance hears it and says "the guy made some noise while tearing some paper".
I am working on a space-based MMO strategy game. In my game, the taxonomy... well, it's player-specific. Each player can name his ship classes any way he wants. There are 5+1 types of ships by size: tiny, small, medium, large and capital. A separate type is Organic ships, which also have 5 size types. Then you have specializations, e.g. scout ship, command ship, gunship, shield ship, repair ship, transport ship, etc. Then you have ship generations, each generation becoming available based on research of a standard ship blueprint. An initial blueprint, once researched, allows you to assign extra points to certain ship attributes (e.g. speed, hitpoints, available power, available processing power, fuel bay size, etc) from a point pool you're getting from that research. This allows players to create unique ships all day long (some would suck more than others, that's for sure but hey, it's freedom to do stupid things). Then you put modules on the ships, and those modules use up mounting points from the attributes. Some modules would only fit certain specializations and ship sizes (you can't fit a capital command room on a tiny scout ship because you don't have enough space, processing power or room).
The situation you are mentioning is still a result of the cost effective mentality. If people are too busy checking the prank calls, it means there aren't enough people hired to do the job. They have to have enough people to accommodate the prank calls AND the legitimate ones.
That's not what it's about. One could imagine a situation where kidnapped people would get their hands on a phone with no SIM card in it (or an inactive one) and dial 911. Take that away and it might kill people. Yes, fraudulent 911 calls are a problem. But I'd rather have 100 of those for each legitimate call from an NSI phone which might save one or more lives.
This is yet another example where cost effectiveness mentality kills people.
Is that a bad thing? I've been wondering why all the whining that EU population is declining (for example). Let it decline. Sure, this might bring some problems in the long term but there's always population pressure from other parts of the world. Yes, maybe within 50-100 years the most common names in Europe would have African or Arabic origins. Maybe the majority in the USA will be of Asian or Central/South American origin. So what?
Slashdot Mirror
Pseudocode.
http://en.wikipedia.org/wiki/P...
Also Drakon charts.
http://en.wikipedia.org/wiki/D...
I actually was taught DRAKON charts (a variation of it) in high school back in '96. It tremendously helped me in more ways than strictly programming (which I never embraced). My teacher used to call it pseudocode back then, although Pseudocode is different.
At the time, generating a high level overview of the processes in DRAKON before building any code was mandatory, and it sped up code generation because you always knew what the next steps would be.
I'm Romanian, you inconsiderate clod!
This means I'm nerdier than you'd think, because I adhere to my country's decimal rules. Ta-daa!
Slashdot-specific:
Heat Wave in India kills 9,1666666666666666666666666666667e-5% of its population.
I have a Facebook account, I am logged in and still can't see the fucking picture.
Last time I checked (last week), 1TB worth of empty BDRs is about twice more expensive than a 2 TB HDD. it's better to buy 2x 1 TB drive, back-up with redundancy and keep them plugged in but powered off, or store them in two different locations.
Very simplistic analogy:
You rip a sheet of paper, it makes noise. Once you finished with it, no noise would ever come out of it, but someone in the distance hears it and says "the guy made some noise while tearing some paper".
You forgot the Bennett whatever-his-last-name-is dump.
His island.
Skip cutscenes by pressing Spacebar.
I am working on a space-based MMO strategy game. In my game, the taxonomy... well, it's player-specific. Each player can name his ship classes any way he wants.
There are 5+1 types of ships by size: tiny, small, medium, large and capital. A separate type is Organic ships, which also have 5 size types.
Then you have specializations, e.g. scout ship, command ship, gunship, shield ship, repair ship, transport ship, etc.
Then you have ship generations, each generation becoming available based on research of a standard ship blueprint. An initial blueprint, once researched, allows you to assign extra points to certain ship attributes (e.g. speed, hitpoints, available power, available processing power, fuel bay size, etc) from a point pool you're getting from that research. This allows players to create unique ships all day long (some would suck more than others, that's for sure but hey, it's freedom to do stupid things).
Then you put modules on the ships, and those modules use up mounting points from the attributes. Some modules would only fit certain specializations and ship sizes (you can't fit a capital command room on a tiny scout ship because you don't have enough space, processing power or room).
No classes. Classes are so... yesterday's jam.
You die anyway.
Give me a logical explanation as to why I shouldn't, then I'll consider it.
The situation you are mentioning is still a result of the cost effective mentality. If people are too busy checking the prank calls, it means there aren't enough people hired to do the job. They have to have enough people to accommodate the prank calls AND the legitimate ones.
That's not what it's about. One could imagine a situation where kidnapped people would get their hands on a phone with no SIM card in it (or an inactive one) and dial 911. Take that away and it might kill people.
Yes, fraudulent 911 calls are a problem. But I'd rather have 100 of those for each legitimate call from an NSI phone which might save one or more lives.
This is yet another example where cost effectiveness mentality kills people.
Maybe you don't know of them but they do exist and have existed in the past in large numbers.
You ever heard of this thing called The Inquisition?
Coca Cola couldn't buy Dr. Pepper either. But that was FTC being against it so it doesn't count :)
Isn't that valid for ALL holy books?
They're all fantasies after all.
Shows how "progressive" some countries can be.
Is that a bad thing?
I've been wondering why all the whining that EU population is declining (for example). Let it decline. Sure, this might bring some problems in the long term but there's always population pressure from other parts of the world.
Yes, maybe within 50-100 years the most common names in Europe would have African or Arabic origins. Maybe the majority in the USA will be of Asian or Central/South American origin. So what?
You mean... a tiny minority?
Um... wat?
I knew all that.
Vast "minority" falls nowhere in there.
You can't DeflatePUSH too much because it will DeflatePOP.
Not to mention that when people find out that the gate was purposely kept in disrepair... there would be another scandal.
Gatesgategategate!
Non-native English speaker here: is there such a thing as a "vast minority"?
I go for AMD if I can.
Why?