I have ever heard that C++ programmers can be devided into two camps. One camp has read 《Effective
C++》, the other not. Similiarly, I think we can say, programmer can be devided into two camps.One camp has
read 《Refactoring》, the other not.
You know, code will be read and modified more frequently than it will be written.The key to keeping code readable and modifiable is refactoring.
Generally speaking, if a programmer has not read 《Refactoring》, he/she will be more inclined to write code hard to read and modify. I have ever read and maintained much bad code like that in our project, but fortunately I have read the book before and can use proper refactoring when it's needed.
So I highly recommend every programmer read this book and try those refactoring:You and your code will
feel much better.
C++》, the other not. Similiarly, I think we can say, programmer can be devided into two camps.One camp has
read 《Refactoring》, the other not.
You know, code will be read and modified more frequently than it will be written.The key to keeping code readable and modifiable is refactoring.
Generally speaking, if a programmer has not read 《Refactoring》, he/she will be more inclined to write code hard to read and modify. I have ever read and maintained much bad code like that in our project, but fortunately I have read the book before and can use proper refactoring when it's needed.
So I highly recommend every programmer read this book and try those refactoring:You and your code will
feel much better.