Code Defactoring

Refactoring is a process that makes code easier to read and change. Therefore, there is a reason to believe that the formulation must be opposite. This is my work today. Early this week, my code was not approved (how wonderful). The problem is that I do not support keyword access control like "private" or "public" like other languages, using some kind of construct to supplement ECMAScript. His view is that access control is destructive, I should rewrite with .prototype so that all members are published, but by comment, documentation and / or some naming conventions obviously "private" simply

Regarding the code, I am STICKLER about formatting. And this is not just me. You will find superior engineers also care about well-formed, clean code. why? First of all, it is easy to read! Encoding is very difficult in some cases, making the code easier to read makes developers' work easier. In addition, writing clean code will send a message to your interviewer, and you are proud of the process of writing code, which is a big problem for many teams. However! It's pretty simple, once you get used it makes your code easier to read, others are easier to read and maintain. Many new developers do not receive much code maintenance, but when you have to clean up the code written by others, you will be more thankful if you organize it properly. I will pay it!

Refactoring is a process that makes code easier to read and change. Therefore, there is a reason to believe that the formulation must be opposite. This is my work today. Early this week, my code was not approved (how wonderful). The problem is that I do not support keyword access control like "private" or "public" like other languages, using some kind of construct to supplement ECMAScript. His view is that access control is destructive, I should rewrite with .prototype so that all members are published, but by comment, documentation and / or some naming conventions obviously "private" simply