Often, when we enter a company, we don't start a project all over again, but rather maintain or develop new features based on existing code, so we have to "read code".

Reading has "general reading" to understand the system architecture, functional modules, a general understanding of the system, each function can find the corresponding code to achieve the location.

There is also "intensive reading", which is usually debugging, used when fixing bugs.

For a mature project, reading code -- not writing it -- is probably the most time-consuming task. time-consuming task for a mature project.

Writing comments and documentation

In order to spend less time "reading code," we have to spend time "writing comments" and "writing documentation" -- one of programmers' pet peeves. -the most abhorrent task for programmers. So now the voice of "bad code only need to comment" has become stronger and stronger, but no matter what, the document still need to write. (Note: it's important to be able to distinguish between comments and documentation)

Understanding Requirements

All right, it's finally time to "write code".

However, before you start writing code, you must take the time to "understand the requirements". Unlike writing a small program for fun, in a company you're writing code for someone else, so you have to understand exactly what that someone else is trying to accomplish. Often, this is not as easy as you might think, and requires a lot of communication.

Of course, there are some teams and individuals who don't want to "waste time" on this, and they usually end up writing code, then changing it, and working overtime to do a lot of useless work, which makes the whole company resentful.