This idea reminds me of "On Error Resume Next".
The reason you don't do that is because a divide by zero indicates that you've got a logic failure somewhere else in your code. It's frequently easier to find an error when it's flashing big and red and throwing exceptions, rather than failing silently.
This reminds me of something one of my professors told me in a computer security course a long time ago. "If you want to make a computer really secure, all you have to do is turn it off, lock it in a safe and throw away the key."
I bet you're a freshman. As mathematics (along with physics) is the foundation upon which computer science is built, you would do well to have a good understanding of it. I'm not saying that you should become an expert or take on a math degree, but, if you don't understand the basic principles underlying the code that you write, then I would have a hard time trusting that code in any meaningful application. Plus, it's not entirely useless in the real world. If you want to do an estimate of an algorithm's running time? Math. Want to compile some statistics on your application's usage patterns? Math.
Amen to this, brother. Maybe the general problem here is that the people who are doing the interviewing aren't the same people who are going to be working with the guy getting interviewed.
In short, no. I tend to run out of steam after about four or five hours, having to stay an extra three or four hours after the eight would just be a waste of time, piss me off and not get anything accomplished. Additionally, he's basically asking you to increase your work time by at least 25% for free. Nice try there, buddy.
Assuming your boss is a reasonable human being (a little difficult to believe considering he even suggested this), you should be able to convince him that this is a horrible idea. Otherwise, start polishing your resume, it's time to jump ship.
Slashdot Mirror
... for appropriate bribery.
This idea reminds me of "On Error Resume Next". The reason you don't do that is because a divide by zero indicates that you've got a logic failure somewhere else in your code. It's frequently easier to find an error when it's flashing big and red and throwing exceptions, rather than failing silently.
This reminds me of something one of my professors told me in a computer security course a long time ago. "If you want to make a computer really secure, all you have to do is turn it off, lock it in a safe and throw away the key."
At least you don't have any kids yet. After that, where you put your gaming PC will be the least of your concerns.
Even a broken clock is right twice a day.
People also use the internet for learning.
I bet you're a freshman. As mathematics (along with physics) is the foundation upon which computer science is built, you would do well to have a good understanding of it. I'm not saying that you should become an expert or take on a math degree, but, if you don't understand the basic principles underlying the code that you write, then I would have a hard time trusting that code in any meaningful application. Plus, it's not entirely useless in the real world. If you want to do an estimate of an algorithm's running time? Math. Want to compile some statistics on your application's usage patterns? Math.
OK, show me the plans for a time machine that can be built with sufficient application of resources.
That's easy. Step 1: Perform any action. Or don't. Step 2: You have traveled through time. Congratulations.
I would counter that any problem is solvable given sufficient application of resources. Also, you're one depressing motherfucker.
Amen to this, brother. Maybe the general problem here is that the people who are doing the interviewing aren't the same people who are going to be working with the guy getting interviewed.
In short, no. I tend to run out of steam after about four or five hours, having to stay an extra three or four hours after the eight would just be a waste of time, piss me off and not get anything accomplished. Additionally, he's basically asking you to increase your work time by at least 25% for free. Nice try there, buddy. Assuming your boss is a reasonable human being (a little difficult to believe considering he even suggested this), you should be able to convince him that this is a horrible idea. Otherwise, start polishing your resume, it's time to jump ship.