|
|

These pages are dedicated to Dr. Mohammad Hossein Ghavamnia. In the memory of the road he showed us.
|
|
|
|
| |
|
|
 |
Note |
|
- I've collected some tips and hints on programming for acm/icpc. Some of them may seem obvious but if practiced regularly would improve overall performance.
- Please help and populate this list. If you have encountered and found out a hint and you think it's useful mail it to me. See info.html for information on how to contact me.
 |
Hints on Teams |
|
- It doesn't matter if a team member is (or thinks) more experienced or less, stronger or weaker; what matters is coordination and corporation and the power of problem solving together. So don' t be very strict about your teammates, just practice more.
- All of the team members must have all of required skills to some extend. It doesn't mean that everyone should do everything very well but should translate, design algorithm, code and test whenever required.
 |
Hints on Practice Sessions |
|
- Practice together, never practice alone for two reasons: learning from each other and finding ways of effective technical communication (learn each other's language!).
- Make functions and methods from highly used codes like IOs and make templates for use in future problems. Even you can print them and take them to the contests. (see java page for an example on a java template).
- Try to use visual environments like Visual C++, IntelliJ Idea instead of dos environments because they have lots of new and useful features like code completes and workspace support (you don't have to open a lot of windows and confused when switching from a problem to another one).
 |
Hints on Contests |
|
- Print the code immediately after each submits whether you gets "yes" or something else.
- If you get "no" the first thing to do is reading the problem another time.
- If you get "time exceeds" check the algorithm.
- Customize the space on your desktop, for example move monitor and case where you think you are more comfortable.
- Highlight important words and phrases with a pen in your problem papers (e.g range of input variables).
- At least two team members work on a problem (never assign one member to solve a problem alone). If someone codes, the other watches him and helps him.
- Always attend the test contest for finding unpredicted events.
- Bring a calculator, dictionary, algorithm books (and your favorite keyboard if it necessary) with yourselves to contest.
- When a problem is solved put all documents (problem papers and prints) in a bag or on the floor.
|
|
|
|
|