The correct posture to solve daily bugs

  1. There are two cases of bug errors:

    ① The console reports an error -> you can locate the error location (I want to see it)
    ② The console does not report an error but cannot achieve the desired function -> there is a problem with the logic of the design code

  2. Priority of problem solution (from high to low)

    ① Solve by yourself
    a. Analyze the error message description of the console -> the number of lines of code that locate the problem -> analyze the possible problems before and after the line of code;
    b. Breakpoint debugging (debug, necessary for development posts) / piling debugging (System .out.println("")); breakpoint debugging is more recommended
    c. If there is no error message in the console

    ②Look for help on the Internet to
    find this problem -> prefer to choose a blog of the nature of the forum (rigorous). The
    blog basically contains three parts: error description -> error reason -> solution (focus is on the second part)

    ③Seek help from classmates
    , everyone who participates in the analysis and discussion can grow

    ④ Ask the teacher
    for help. The defect is that when the teacher wants to help too many students, the reason may not be analyzed.

Guess you like

Origin blog.csdn.net/weixin_44997802/article/details/108763675