UM High School Programming Competition.
Mar. 6th, 2004 06:21 pm![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
ibnekoRM - solved 3 problems, got 9th (although we would have had 5th if stupid judges/judging-computers didn't randomly delete our working solution at time≈25 min from the start (winning-based on a. number of submitted problems, then if tied on a, then b. total time required for all submissions.)
Mmmm, good job all. Next year, I'd suggest you guys get the code to the other problems not being worked on by the person at the computer printed out onto paper - so you can start writing the code immediately instead of waiting for the person at the computer to finish. Because it was problematic trying to figure out what you guys meant in your how-to-solve-this-problem... I mean, it was helpful, but I still had to re-read the problem until I figured out what it was asking for. -.-;; Not says you guys were bad or anything, it would just have been more helpful... that way I would have been able to focus on debugging errors in your code instead of figuring out how to write it+debugging. Saves some time, you know.
Brain actually shut down about 2 hours into the competition... had to keep mentally prodding my brain to get it to think. I believe sharon saw me doing this :D
Oh, and eclipse can suck my ass. Stupid program kept being stupid. If we had codewarrior, we could have worked a hell lot faster with less having to close and re-open eclipse. Same with the stupid judges. My programs that I submit do run CORRECTLY, damnit. :P
All in all, I'm happy, and pretty proud of us. :) don't mind my complaints, that's just me keeping high expectations.
::yawns:: My head hurts, too much thinking. Dinner now.
Mmmm, good job all. Next year, I'd suggest you guys get the code to the other problems not being worked on by the person at the computer printed out onto paper - so you can start writing the code immediately instead of waiting for the person at the computer to finish. Because it was problematic trying to figure out what you guys meant in your how-to-solve-this-problem... I mean, it was helpful, but I still had to re-read the problem until I figured out what it was asking for. -.-;; Not says you guys were bad or anything, it would just have been more helpful... that way I would have been able to focus on debugging errors in your code instead of figuring out how to write it+debugging. Saves some time, you know.
Brain actually shut down about 2 hours into the competition... had to keep mentally prodding my brain to get it to think. I believe sharon saw me doing this :D
Oh, and eclipse can suck my ass. Stupid program kept being stupid. If we had codewarrior, we could have worked a hell lot faster with less having to close and re-open eclipse. Same with the stupid judges. My programs that I submit do run CORRECTLY, damnit. :P
All in all, I'm happy, and pretty proud of us. :) don't mind my complaints, that's just me keeping high expectations.
::yawns:: My head hurts, too much thinking. Dinner now.
![[identity profile]](https://www.dreamwidth.org/img/silk/identity/openid.png){kind=small}
no subject
Date: 2004-03-06 03:38 pm (UTC)You're right about writing out the code ahead of time, the 'algorithm' for #6 was far too vague. I think having just one practice session ahead of time would have helped -- getting used to the idea of writing out the problems on paper, since we always program by ourselves and by experimentation and don't always plan things out.
You looked to me like you were literally prodding your brain to think. ^^
no subject
Date: 2004-03-08 03:10 pm (UTC)Nah, you guys aren't stupid.
no subject
Date: 2004-03-08 03:13 pm (UTC)Now that I stop and try to picture that... I think the universe would probably implode.
no subject
Date: 2004-03-08 03:15 pm (UTC)