PSet2 FAQ
From 6.006 Wiki
(Difference between revisions)
m |
|||
Line 1: | Line 1: | ||
+ | = PSet2 = | ||
== Questions == | == Questions == | ||
Line 4: | Line 5: | ||
Running times for Part A: | Running times for Part A: | ||
- | ==general debugging hints== | + | == Common Mistakes == |
+ | |||
+ | == general debugging hints == | ||
* adding asserts to your code can help you to ensure that values are what you expect them to be at all times | * adding asserts to your code can help you to ensure that values are what you expect them to be at all times | ||
Revision as of 20:42, 4 October 2008
Contents |
PSet2
Questions
Staff solution info
Running times for Part A:
Common Mistakes
general debugging hints
- adding asserts to your code can help you to ensure that values are what you expect them to be at all times
- write your code modularly: use submethods for any non-trivial repeated or similar code.
- write unit tests for each of the submethods written
- separate complicated computations into smaller pieces which can then be asserted on.
- try to find out where the time is going, are some methods being called more often than you expect them to? do they take longer to execute than expected?