I wonder if anyone prepared a check list that makes it easy to quickly spot the problem in the exam. The most important thing in answering a question is to figure out what feature is being tested.
If the code snippet has plenty of logic and a compile time error, it doesn't make any sense to spend time looking at the logic only to realize that it finally results in a compile time error, for example.
I know it is very hard to prepare such an exhaustive list since there are so many things to look for. However, it still helps if someone came up with atleast a subset of some of the most obvious errors. I hope this kind of list infuses some kind of discipline into the way the exam questions are aced.
What I am looking for is something like... 1. What is the first thing we need to look for to ace an exam question 2. What is the second thing we need to look for to ace an exam question . . . n.
Please share if you have any info regarding the list discussed above. Thanks in advance. Looking forward to your replies.
I am not sure if such it's possible to come up with such a list. Because such list will only apply to questions that are between easy and medium difficulties. For harder questions, there is probably not a very easy way to solve it, except... solve it. Besides, the amount of variations the authors can put down will be thousands.... so if there were such a list, it will be at least be thousand items long. In the end, going through such a list, will be like going through a book. So might as well just do tons of mock exam questions and read good books instead.
I think the closest thing to what you are looking for is the quick notes, K&B book comes with it after each chapter, that might be more helpful. [ October 25, 2007: Message edited by: Tony Smith ]