Challenge 5: Army Time

[jeepnut]

Originally Posted by manasecret

Jeepnut, you got the most points out of anyone. You had like a ten point roll there for awhile, and then like ten more right after that but broken up every once in awhile. What was your secret, sir?

I tried my best to figure out the exact time to post according to my wristwatch. Turns out if I clicked post reply halfway between 41 and 42 seconds on my watch, I usually got it. You were rolling too for a while. Were you using the same method?

[manasecret]

Originally Posted by jeepnut

I tried my best to figure out the exact time to post according to my wristwatch. Turns out if I clicked post reply halfway between 41 and 42 seconds on my watch, I usually got it. You were rolling too for a while. Were you using the same method?

Haha, yep, except I was using my Windows system clock, which also has that second hand in there. I had it figured out early on that I needed to click sometime between 53 and 54 seconds, but closer to the 53 side. Wristwatch was probably better, since the length of the Windows seconds would vary slightly, since the CPU is too busy doing a bunch of other crap for it to be exact.

Then I figured out using the mouse would sometimes cause me to miss the button. So I used Tab to highlight the button and all I had to do was press Enter on the keyboard.

[thatmariolover]

Originally Posted by manasecret

Haha, yep, except I was using my Windows system clock, which also has that second hand in there. I had it figured out early on that I needed to click sometime between 53 and 54 seconds, but closer to the 53 side. Wristwatch was probably better, since the length of the Windows seconds would vary slightly, since the CPU is too busy doing a bunch of other crap for it to be exact.

Then I figured out using the mouse would sometimes cause me to miss the button. So I used Tab to highlight the button and all I had to do was press Enter on the keyboard.

Haha I was doing the same thing. But you're right, it's slightly off. Honestly though, there's no excuse for that. There should always be enough CPU to do an accurate measurement of time.