This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
Hi all, I've often wondered about this - is there a correct way to read code in exam questions? Do you start from the top and work your way down, or do you locate the main() method (if there is one)and work from there? Which method can you suggest that works best?
I have a different approach, but I don't know if it would help you. When I did the mock exams I found I got a lot of questions wrong because of what I didn't pay attention to in the code. Whenever I answered the question, I forced myself to go back and look at every modifier, and particularly made sure I identified static versus instance members. I'd ask myself if I'd seen something that would change my answer to the question. I found that helpful, but your mileage may vary.
Reid - SCJP2 (April 2002)
Joined: Jan 23, 2002
Thanks guys. I seem to be overlooking silly mistakes in certain bits of code. I think I need to get into some routine of double checking one line at a time to spot these pit-falls.