Neat code vs dirty code
Posted in category [Software engineering]
8 Tips for Great Code Reviews
I recently participated in several code review sessions. During the review process, I found that some problems appeared almost every time. I picked a few typical questions to explain. These questions are all primary problems and the solutions are easy. As long as you master the method and consciously avoid it, you can quickly improve the code quality in a short time. The so-called small investment, quick results.
Ccode review is an important part of the developer’s daily work, the value of code review – why, when, and how?
What is the relationship between design, architecture, and framework?
Somethings about code review you need to know.
The technology and practice of software engineering is divided into two parts, one part is consistent with the book knowledge, about half, this part can be learned basically in the university, self-study as long as the method is appropriate, hard work can also be the way; but the second part comes from In actual teams, experience, content is usually not available from books, and it is difficult to say right or wrong, different people and different experiences have created different understandings. The code review is a typical part of the second part, which can be discussed in a big way.