Big project did not write, at most a project 2000 lines of code, so I think do the main, or do a good job of the wrong way to see the naked eye, the output of intermediate results although can quickly lock the position, but sometimes miss the deep-seated bug
The most impressive one is to play the ACM problem, the array opened small, leading to the wrong one afternoon, I think to plan to check the wrong time, not more than 20 minutes appropriate. It's easy to get into a dead loop for a long time.
Here are a few blog links I have written about the specific problem analysis
http://blog.csdn.net/c337134154/article/details/48938833
http://blog.csdn.net/c337134154/article/details/48862341
http://blog.csdn.net/c337134154/article/details/48788685
Then is the summary:
http://blog.csdn.net/c337134154/article/details/47908407
First job of software testing