[150929] 2nd personal Blog Job

Do you need code specifications?

I met a good opportunity to practice at a company in Seoul. Sophomore, almost no programming level, but that company needs to understand the Chinese programmer-I am very fortunate to be the first Chinese-speaking programmer of that company (should be the first to understand the Chinese language of the development staff-because I am an intern). So I had the opportunity to take part in projects, get in touch with multiple languages and a variety of code, and also participate in team projects. The importance of coding specifications and coding styles was felt at the time.

Each programmer has different coding styles and specifications. What is needed in a team project is to make each code look like it was written by a single person. That is, to write easy-to-read code that makes it easy for other members to modify and maintain. The reason a team needs to have a uniform coding rule (coding rule) is that first, in order to improve the readability of the code, second, in order to reduce errors caused by errors. Many programmers may resent coding rules, but I think coding rules are necessary because software development has long been a division of labor between people. If it's a personal software project, it's a good choice to have coding rules, because people's memories will blur over time. Generally speaking, coding specifications are important in the programming process, whether it's a multi-person development project or a personal development project.

Coding rules are not necessarily the order to be obeyed, but they will certainly benefit many people and help improve the overall productivity of the team. It may take a while to "wear a new dress" for a while, but for an ideal person, if the "new dress" can make him avoid a lot of harm, there is no more important reason not to let him invest a little energy to choose the new dress.

Code review

Continued

[150929] 2nd personal Blog Job