2 ms·
I approach tests by going to the next question if the answer isn't immediately solvable. Then, when reaching the end, I go back and spend more time on the ones
by WalterBright 3y ago
I approach tests by going to the next question if the answer isn't immediately solvable. Then, when reaching the end, I go back and spend more time on the ones I hadn't solved. That maximizes the score.
I apply that technique everywhere. For example, when working the bug list, I'll solve the easy problems first, and the toughest last. That also maximizes the score, as the bug submitter's only care is if the bug is fixed, not how hard it is to fix.
- nick__m 3y agoAlmost completely off topic but you are good example of nominative determinism !
- WalterBright 3y agoIn the Air Force, my dad's assigned office mate was Major Smart. A line of my ancestors were the Dumbles.
- LanceH 3y agoWhile in the Marines, I knew of a Major Hazzard and a Captain Justice. I really wanted to be there when they first met.
- remram 3y agoGiven a fast enough supply, this means you never look at the difficult bug reports at all.
- WalterBright 3y agoIt also clears the mind if one clears out the easy ones first. It's like when I feel like working on the car, the first thing is clean the garage. (If the reports come in faster than they can be fixed, of course one can never catch up regardless of the algorithm.)
- sverhagen 3y agoIn (software) engineering you want to take on enough of the hard stuff early on, to make sure you're not painting yourself into a corner with naive solutions...
- WalterBright 3y agoThere is always the concern that one has made a fundamental error. Can't worry about it too much, though, or one will never get anywhere.
- dsego 3y agoI applied this to school tests but not in my work, well sometimes, if I'm procrastinating and need a few quick wins. But for timed tests, it's essential to skip something you're struggling with and get some points on the other questions.