I love this puzzle because the answer doesn't seem to make sense at first. The best thing about this puzzle, though, is how many people got worked up emotionally over the solution provided and wrote to the paper to "correct" vos Savant. There was a great story about it in one of her books (can't be arsed to look it up).
I hate you. It's that simple?! After working on it for an hour, I came up with a solution that worked all the time, or so I thought. I then realized it was wrong after reading someone else's post and trying it again. Now I read yours and realize the trick to it.
I should've tested my idea a bit more to realize it was flawed, and then fixed the problem and simplified it before reading these comments. (My "solution" worked because statistically there is a good chance it works out the right answer most of the time. Heh, now that's reasonable engineering if it is within the fault tolerance!:-D)
I don't know what they'll offer users over other IM systems, but I bet they will mine conversations for general buzz that they can then sell to companies who are interested in what consumers are talking about. Just from sociological standpoint, it would be interesting to see if there are any common topics being discussed at any point in time. Like with gmail, there will be privacy concerns, but they'll probably argue that they will not tie together people directly to conversations and that they will have some bots combing through the talks versus human beings.
Hey, yeah, I'm the same way. Even in my last-last job (not as an intern), whenever there was down time, I took the opportunity to read papers our Ph.Ds were reading and tried formulating my own ideas for use. Unfortunately, it still takes lots of work to get your ideas put into practice due to politics and bureaucracy.
I did internships a few years ago (yikes, I feel old) at three different companies. Regardless, of the company, I highly recommend them for obvious reasons, i.e. you get great work experience.
One tip I would give, though, is that wherever you do end up working, you are going to have to prove that you can take on challenging tasks. No matter how smart they are or think they are, companies who hire interns assume interns aren't very knowledgeable and aren't responsible enough to take on more challenging tasks. I can see where they are coming from, so I don't dispute the validity of their actions. With that in mind, if you really are good, don't be afraid to ask for more work, and more interesting stuff at that. I've found that in the past, I was able to breeze through tasks and was quickly bored. Initially, I was too shy and lacked confidence to ask for something more difficult, so I "wasted" my first internship by repeatedly doing simple things they tossed at me because I thought that I shouldn't rock the boat.
Also, don't be surprised to find that you are left on your own and have nobody to hold your hand through things. I've never worked anywhere where somebody has always been around to help answer questions or knew enough to answer all my questions. But then, that's the reality of the work (and "real") world.
I remember even back at IBM in 2000, before they really embraced open source, I was using some GNU tools (not source) to help with an internal project. Before we formalized the tools I was creating (okay, they wanted to patent it), they asked that I make sure we didn't make use of anything that would require us to open our tools to the world. This was strange as I wasn't using any source code and was simply using tools that were freely available.
Of course now, I'm sure (at least I hope) they're more aware of what goes into the various open source licenses.
If we cannot engage in hijinx on public transit, then the terrorists have won!! We cannot let them win! LET TEH HIJINX BEGAN!!!!!!!!11111onehundredeleven
I guess I meant it was really long. I agree with you that it was enjoyable. It was just such a long day. Once I got into the groove of answering questions and tackling code, it was fun. It's like you want to show off to them.
Interestingly, only my last interview (of a half-dozen) covered any behavioural questions. Almost all the interviews before that were all technical, coding-on-a-whiteboard type questions. It's pretty grueling, actually.
I love this puzzle because the answer doesn't seem to make sense at first. The best thing about this puzzle, though, is how many people got worked up emotionally over the solution provided and wrote to the paper to "correct" vos Savant. There was a great story about it in one of her books (can't be arsed to look it up).
The sound of one hand clapping.
I hate you. It's that simple?! After working on it for an hour, I came up with a solution that worked all the time, or so I thought. I then realized it was wrong after reading someone else's post and trying it again. Now I read yours and realize the trick to it.
:-D)
I should've tested my idea a bit more to realize it was flawed, and then fixed the problem and simplified it before reading these comments. (My "solution" worked because statistically there is a good chance it works out the right answer most of the time. Heh, now that's reasonable engineering if it is within the fault tolerance!
Yeah, I hope they're doing some sort of motion-based stitching where each frame brings in some more pixels in the overall image.
Looks like Satoru Iwata found it.
He's a numerologist.
I don't know what they'll offer users over other IM systems, but I bet they will mine conversations for general buzz that they can then sell to companies who are interested in what consumers are talking about. Just from sociological standpoint, it would be interesting to see if there are any common topics being discussed at any point in time. Like with gmail, there will be privacy concerns, but they'll probably argue that they will not tie together people directly to conversations and that they will have some bots combing through the talks versus human beings.
Yup, I thought it was a Google Alert-like system for patents in the queue that may be harmful in the near future.
Hey, yeah, I'm the same way. Even in my last-last job (not as an intern), whenever there was down time, I took the opportunity to read papers our Ph.Ds were reading and tried formulating my own ideas for use. Unfortunately, it still takes lots of work to get your ideas put into practice due to politics and bureaucracy.
I did internships a few years ago (yikes, I feel old) at three different companies. Regardless, of the company, I highly recommend them for obvious reasons, i.e. you get great work experience.
One tip I would give, though, is that wherever you do end up working, you are going to have to prove that you can take on challenging tasks. No matter how smart they are or think they are, companies who hire interns assume interns aren't very knowledgeable and aren't responsible enough to take on more challenging tasks. I can see where they are coming from, so I don't dispute the validity of their actions. With that in mind, if you really are good, don't be afraid to ask for more work, and more interesting stuff at that. I've found that in the past, I was able to breeze through tasks and was quickly bored. Initially, I was too shy and lacked confidence to ask for something more difficult, so I "wasted" my first internship by repeatedly doing simple things they tossed at me because I thought that I shouldn't rock the boat.
Also, don't be surprised to find that you are left on your own and have nobody to hold your hand through things. I've never worked anywhere where somebody has always been around to help answer questions or knew enough to answer all my questions. But then, that's the reality of the work (and "real") world.
Super Mario Bros. 3
"You've got UnixWare in my Linux!"
"And you've got Linux in my UnixWare!"
"AAAAAAaaaaaaaaaaaaaaaaaahhhhhhhh!!!!!!!"
Ah, so it's all about known knowns and known unknowns? They should consult with Donald Rumsfeld on this!
Argh!! Now I know how the comic strip ends.
I remember even back at IBM in 2000, before they really embraced open source, I was using some GNU tools (not source) to help with an internal project. Before we formalized the tools I was creating (okay, they wanted to patent it), they asked that I make sure we didn't make use of anything that would require us to open our tools to the world. This was strange as I wasn't using any source code and was simply using tools that were freely available.
Of course now, I'm sure (at least I hope) they're more aware of what goes into the various open source licenses.
I don't care how snappy it is. If your OS is having the "runs", you've got bigger issues.
Haha, that's awesome. Too bad about the caller ID spoiling it.
And I'll be the Director of Midget Technology.
Does it feel snappier than the previous version?
I wouldn't go that far. However, MSSHELL.EXE ought to be good enough for anybody.
You're right, but you can also right click while holding down the left click button to cancel your action.
If we cannot engage in hijinx on public transit, then the terrorists have won!! We cannot let them win! LET TEH HIJINX BEGAN!!!!!!!!11111onehundredeleven
I guess I meant it was really long. I agree with you that it was enjoyable. It was just such a long day. Once I got into the groove of answering questions and tackling code, it was fun. It's like you want to show off to them.
Interestingly, only my last interview (of a half-dozen) covered any behavioural questions. Almost all the interviews before that were all technical, coding-on-a-whiteboard type questions. It's pretty grueling, actually.
No, but a slashdot can detect a < and remove it if it thinks it's an attempt at bad HTML.