Zhongcheng online-reconstruction-Excellent programmer cultivation (note 4 we started to enter intensive training after spitting out)

There are 22 bad tastes in refactoring. I will explain them one by one.

Wait !!! You made a mistake !!!

 

80% principle: Our 20% Code only violates the bad taste of 20%, so we only need to learn the and do it well, then you are a good programmer.

 

"I am not a great programmer. I am just a programmer with many good habits." ---- Kent Beck

 

 

20% bad taste:

1. Duplicate duplicated code

2. The long method is too long.

3. Large class is too long

4. long parameter list: List of too long parameters

5. Switch statements switch shocking appearance

 

Reinforcement... (this part cannot be written as a blog, but it is the most important and most important)

 

Next, let's strengthen the following five

6. Shotgun surgery Modification

7. Feature envy attachment

8. Data clumps data dashboard

9. Basic primitive obsession type paranoia

10. Divergent change divergent change

 

Do you want to finish all 22 courses? In my personal opinion, the rule tells us "what is done, what is not done ". For the team, the biggest benefit ratio can be obtained for enhanced training with 20% bad taste. For individuals, you can learn the remaining 80% based on your interests.

 

Finally, let's be encouraged by some masters in reinforcement.

 

Clean code is only good for one thing---- Bjarne stroustrup

Clean code is simple and straightforward---- Grady booch

It only provides one, not multiple ways to do one thing---- Dave Thomas

Neat code always looks like something someone cares about it, and there is almost no room for improvement.---- Michael feathers