It doesn't really work that way because TV shows and movies have a lot of sound in the high and low ranges, while commercials have more in the mid ranges. A decibel of sound in the high or low ranges can seem quite while a decibel in the mid ranges can seem loud, depending on the TV and the listener.
Further, if a TV show was extremely quiet, the commercial would be forced to be quiet...
-Thomas
During my internship, I worked on a University research project in games and ended up building the material for the first "games" themed CS course at the U of A. I finished my CS degree next year and now I'm a game programmer at Bioware.
I disagree with your comment that the course will sucker students. If the course is sufficiently difficult (as other CS courses are) it will weed out the disinterested. I know a couple of students who weren't great at Math but because excellent at it once they understood it in the context of a physics engine.
Personally, my feedback would be: Games related courses would be incredible useful, but profs are not incredibly good at creating them. Games programming is about hacking solutions, designing for fun rather than correctness, and project management for short deadlines. CS profs aren't known for any of those things.
Appears to control or at least influence the logical flow of the election
What exactly does that mean?
Means they suspect that the code for the actually tallying and evaluating ballots is in SQL. It is suggested that this violates the law for being dynamic and interpreted.
"If I don't win the lottery, I'm turning on the LHC."
Fantastic!
I tried to write a similar story in university:
step 1) The scientist is born.
step 2) The scientist goes through the time machine, and kills his grandfather.
step 3) The scientist is not born.
step 4) The grandfather is not killed.
step 5) The scientist is born
step 6) The scientist goes through the time machine, and kills his grandfather
(the timeline replays in countless variations, like Groundhog day)
step 39,834,234) Eventually, (possibly quantum) variations in the loop will produce an unlikely event, ie, the scientist dies, the time machine fails, etc.
From the outside perspective, the scientist was never able to achieve time travel, and the proliferation of nasty accidents around time travel experimentors would seem like some sort of "Physicist's Curse".
Eventually, that was adapted for a Neverwinter Nights module, where dragons were wiped out thousands of years ago, and a young magician is trying to bring them back (thus creating a paradox in history) and a similar "time loop" where you must redo the same day over and over until you stop the magician from creating the time portal.
If the clone was intended to replace you since your body was feeble or damaged, then I'd say great, get on with it. Fear of death is an irrational instinct in that situation, the same as the fear of a painful needle. (Unless you are a spiritual person, but if you are, then you have to deal with your own special magic and I can't answer for you.)
Now if the original body was helpful... I'd say, "Hey! Let's go finish that deck, we'll get it done twice as fast with two of us."
Do you work in the games industry?! That's a really weird interpretation of "design." (I work at a AAA game studio, by the way)
There are so many ways I want to go on this one:
1) That's a really naive interpretation. If you're going to use an architecture analogy, you can't compare the programmers to construction workers. Level designers and combat designers are the construction workers. Do you even know what a civil engineer does? System designers and Programmers are more like that. The Lead Designer is more like an architect, and he wouldn't have a clue what was possible if it weren't for the Lead Programmer or tech director.
2) DAIKATANA.
3) Programmers make way more money than the average designer (check salary surveys), because it takes years of training to even go near games. There are high and low level designers, and the majority of design are low level and make less.
4) Do you realize that the majority of man-hours of grunt work are spent on tech design, level design, and combat design?
That's like saying "Racecar drivers are the core of racing. Engineers are a dime a dozen." Or "Screenwriters are the core of film. Directors are a dime a dozen." You think programmers just sit there building things that other people told them to? That's so incredibly misinformed.
But then how does a person break into the industry?
The above question was rhetorical. You break into the industry by getting an entry level job. Then you work for 6 months, and get your promotion to the second level, or switch to a better job. 2 years later you have "experience."
Start with what you love. The money will come later.
A morsel of genuine history is a thing so rare as to be always valuable. -- Thomas Jefferson
