Wide, crazy eyes and frantic button mashing mean that the CPU should be overclocked as much as possible, while closed eyes mean that the system should ignore changing the CPU frequency, and send a System Beep straight through the headphones.
I didn't know what it was either, so I looked through the YouTube comments on the video (I linked to the higher-quality version), and I found the answer:
"James disappears from the stage for long periods of time during extended solo parts...the running joke among DT nerds is that he digs a massive hole during instrumental breaks"
If chemicals induce vomiting, they are affecting your health... repeated vomiting can have some nasty effects (like difficulties breathing due to rib muscle injury, or major capillary damage that can affect eyesight, or aspiration of stomach contents leading to pulmonary infection).
Don't forget vocal chord rupture. James Labrie of Dream Theater had this happen after eating in Cuba and getting food poisoning. Ten years later, he was fully recovered. In the meantime, he had nowhere near the vocal range that he used to. (parodied in the James Labrie Action Figure commercial)
As a former chemist, I'm willing to smell something, but I never let anyone stick something in my face; if I'm going to smell something, it's either going to be on a flat surface, or in MY hand. Then I "waft" the scent towards my nose from a good distance with my hand, and if I still can't smell anything, then I might go closer.
My last employer was decently small (~100 people), and there were strict rules to try to prevent this problem:
If it has no name, throw it out, even if it's not yours. If it has a name but no date, ask the person about it, and throw it out if they don't say "keep it". If they tell you they'll take care of it, don't believe them. If it has a name and an old date, ask the person about it, and be prepared to throw it out. Every month or so, send out an e-mail saying "Everything in the fridge gets thrown out by the end of the day.", and then do it.
My current employer is a larger company, and just has a policy of emptying all fridges at the end of every week.
I don't think it does, but my parent poster implied that there's a perceptible difference. I was just correcting him, saying even if there was, he had it backwards.
If he meant human efficiency, not computational, then I'd say he definitely had it backwards, as installing ABP and letting it self-update is much easier even than downloading a pre-made hosts file every so often.
As someone said above: if you wish to block all ads forever, then you might consider a fork of ABP. However, the extension was originally started to put the balance of power between webmasters and users back in the middle, and to encourage advertisers to use less annoying ads that users would be less likely to block.
IMO, this would be along the lines of the reasoning that led him to start the extension in the first place.
In contemporary usage, memory usually refers to a form of semiconductor storage known as random access memory (RAM) and sometimes other forms of fast but temporary storage. Similarly, storage today more commonly refers to mass storage - optical discs, forms of magnetic storage like hard disks, and other types slower than RAM, but of a more permanent nature. Historically, memory and storage were respectively called primary storage and secondary storage.
In the past, RAM might have been called "primary storage", but nowadays "storage" refers only to permanent solutions. Using historical terminology in conversation without context is a pretty easy way to confuse people. To me, your use of "storage" to include cache and RAM is similar to the use of the term "processor" to mean anything other than the CPU, without further context to clarify the word.
Don't blacklist anyone; just make your interview process more thorough.
It doesn't matter if someone got their degree from MIT or the University of Pheonix; if they show you in the interview that they can actually design good software, hire them.
Memory is a type of storage, essentially, but you're not using standard conventions for the vocabulary. Storage is permanent, like hard drives, tape drives, and optical disks.
Saying that storage is a bottleneck, and including memory, is like saying that the "processor" is the bottleneck for pretty much all games today. If I correct you, saying that it's the GPU, you can try to argue that you're still right, since the GPU is a processor, but you're just confusing the issue.
You're right, that's not really an algorithm issue on its face, but there's still a lot of performance consideration.
This brings up a point from that "old language conventions" article a couple weeks ago; I've been writing so much code in high-level languages that the low-level stuff has been pushed to the back of my mind. I can just create a data structure and say "tree.sort()".:)
I think in a high-level language all I have to really know is what the best data structure is for a given usage of the data, but I learned all that thanks to my school experience with lower-level languages.
I may not have the QuickSort algorithm memorized, but if I needed to manually sort a data structure in a lower-level language, I'm decent enough of a programmer that I can take what I read from a book or online, and adapt it to the current situation.
I made a bad example, but we did learn how to analyze algorithms, what Big-O notation is, and how to use the basic data structures efficiently (mostly in the Data Structures class, which is taught at the sophomore level).
The land covered by Sacramento involves quite a bit of the outlying land that has essentially nothing on it. The built-up downtown area is much denser than the outlying land, and that's what I was talking about.
Paris, on the other hand, covers quite a bit of land, and the population is fairly uniformly distributed.
Some professors would dock us points for using inefficient algorithms, especially in the higher-level courses like Programming Languages, and OO. Of course, the C/Asm course also dealt quite a bit with the most efficient way to do things when you're working at the low-level.
One example from the Java section of Programming Languages, despite being written in a high-level language: having a loop append to a String is very expensive, so using a StringBuilder is a much better practice.
I'll also note that I took AI myself, but that was a CS Elective course.
Links > Lynx
Well, there are rumors that IE8 is the last version before MS cancels it...
Wide, crazy eyes and frantic button mashing mean that the CPU should be overclocked as much as possible, while closed eyes mean that the system should ignore changing the CPU frequency, and send a System Beep straight through the headphones.
I didn't know what it was either, so I looked through the YouTube comments on the video (I linked to the higher-quality version), and I found the answer:
"James disappears from the stage for long periods of time during extended solo parts...the running joke among DT nerds is that he digs a massive hole during instrumental breaks"
So that answers that... :)
Hold the container in your hand, or place it on a flat surface. The point is, if I'm smelling something, I'm not letting someone stick it in my face.
If chemicals induce vomiting, they are affecting your health... repeated vomiting can have some nasty effects (like difficulties breathing due to rib muscle injury, or major capillary damage that can affect eyesight, or aspiration of stomach contents leading to pulmonary infection).
Don't forget vocal chord rupture. James Labrie of Dream Theater had this happen after eating in Cuba and getting food poisoning. Ten years later, he was fully recovered. In the meantime, he had nowhere near the vocal range that he used to. (parodied in the James Labrie Action Figure commercial)
As a former chemist, I'm willing to smell something, but I never let anyone stick something in my face; if I'm going to smell something, it's either going to be on a flat surface, or in MY hand. Then I "waft" the scent towards my nose from a good distance with my hand, and if I still can't smell anything, then I might go closer.
Acid fumes teach you that lesson real quick.
My last employer was decently small (~100 people), and there were strict rules to try to prevent this problem:
If it has no name, throw it out, even if it's not yours.
If it has a name but no date, ask the person about it, and throw it out if they don't say "keep it". If they tell you they'll take care of it, don't believe them.
If it has a name and an old date, ask the person about it, and be prepared to throw it out.
Every month or so, send out an e-mail saying "Everything in the fridge gets thrown out by the end of the day.", and then do it.
My current employer is a larger company, and just has a policy of emptying all fridges at the end of every week.
You small-handed freak...
I can hold a full-size ATX board in each hand, without spilling over! I mean, honestly. What's the big deal?
My mom was at church the day after the Old Man fell. She heard one of the older ladies in the town utter the following phrase:
"It's like nine-eleven all over again..."
[/facepalm]
I don't think it does, but my parent poster implied that there's a perceptible difference. I was just correcting him, saying even if there was, he had it backwards.
If he meant human efficiency, not computational, then I'd say he definitely had it backwards, as installing ABP and letting it self-update is much easier even than downloading a pre-made hosts file every so often.
It's more efficient to block the requests at the application than to have to call down to the OS for a DNS translation.
As someone said above: if you wish to block all ads forever, then you might consider a fork of ABP. However, the extension was originally started to put the balance of power between webmasters and users back in the middle, and to encourage advertisers to use less annoying ads that users would be less likely to block.
IMO, this would be along the lines of the reasoning that led him to start the extension in the first place.
If that dress code requires top hats, though, it's not terribly reasonable.
Wow. I'd shop at that store every day of the week!
Your ideas are intriguing to me and I wish to subscribe to your newsletter.
Who said cell phone?
My parent post:
to his cell phone bill
Not many people had cell phones back in the day when OJ Simpson was being pursued in his white Bronco.
From the Wikipedia article on computer data storage:
In contemporary usage, memory usually refers to a form of semiconductor storage known as random access memory (RAM) and sometimes other forms of fast but temporary storage. Similarly, storage today more commonly refers to mass storage - optical discs, forms of magnetic storage like hard disks, and other types slower than RAM, but of a more permanent nature. Historically, memory and storage were respectively called primary storage and secondary storage.
In the past, RAM might have been called "primary storage", but nowadays "storage" refers only to permanent solutions. Using historical terminology in conversation without context is a pretty easy way to confuse people. To me, your use of "storage" to include cache and RAM is similar to the use of the term "processor" to mean anything other than the CPU, without further context to clarify the word.
Can you explain what you meant? What I read was that you said memory performance was a part of the current storage bottleneck that we must overcome.
If this isn't what you meant, can you explain further?
Don't blacklist anyone; just make your interview process more thorough.
It doesn't matter if someone got their degree from MIT or the University of Pheonix; if they show you in the interview that they can actually design good software, hire them.
Memory is a type of storage, essentially, but you're not using standard conventions for the vocabulary. Storage is permanent, like hard drives, tape drives, and optical disks.
Saying that storage is a bottleneck, and including memory, is like saying that the "processor" is the bottleneck for pretty much all games today. If I correct you, saying that it's the GPU, you can try to argue that you're still right, since the GPU is a processor, but you're just confusing the issue.
You're right, that's not really an algorithm issue on its face, but there's still a lot of performance consideration.
This brings up a point from that "old language conventions" article a couple weeks ago; I've been writing so much code in high-level languages that the low-level stuff has been pushed to the back of my mind. I can just create a data structure and say "tree.sort()". :)
I think in a high-level language all I have to really know is what the best data structure is for a given usage of the data, but I learned all that thanks to my school experience with lower-level languages.
I may not have the QuickSort algorithm memorized, but if I needed to manually sort a data structure in a lower-level language, I'm decent enough of a programmer that I can take what I read from a book or online, and adapt it to the current situation.
I made a bad example, but we did learn how to analyze algorithms, what Big-O notation is, and how to use the basic data structures efficiently (mostly in the Data Structures class, which is taught at the sophomore level).
The land covered by Sacramento involves quite a bit of the outlying land that has essentially nothing on it. The built-up downtown area is much denser than the outlying land, and that's what I was talking about.
Paris, on the other hand, covers quite a bit of land, and the population is fairly uniformly distributed.
Some professors would dock us points for using inefficient algorithms, especially in the higher-level courses like Programming Languages, and OO. Of course, the C/Asm course also dealt quite a bit with the most efficient way to do things when you're working at the low-level.
One example from the Java section of Programming Languages, despite being written in a high-level language: having a loop append to a String is very expensive, so using a StringBuilder is a much better practice.
I'll also note that I took AI myself, but that was a CS Elective course.
It's worse than you think:
NT4 -> 4
2000 -> 5
XP -> 5.1
XP-64 -> 5.2
Vista -> 6
7 -> 6.1
So if they call the next retail product "Windows 8", it'll have the "Windows Kernel 7". How's that for confusing?
I say we try to stomp em with The Boot.