10 most controversial programming ideas

10 of the most controversial programming ideas:
1. The only "best practice" You shoshould be using all the time is "Use your brain ".
The only "best practice" does not use a variety of design methods, models, and frameworks summarized by our predecessors. The famous methods, models, and frameworks only mean that many people agree with them, it does not mean that they are suitable for you. You should use your brain in more regions and think independently about the reasons for the appearance of those methods, models, and frameworks and the ideas and thoughts behind them, that is "best practice ".
2. programmers who don't code in their spare time for fun will never become as good as those that do.
If you are not happy with programming and do not program in an entertaining way when you are idle, you are simply dealing with your work, even if you are a very intelligent and talented person, you will not become a good programmer, either just be ordinary, or will only become a nerd in technology all day.
3. Most comments in code are in fact a pernicious form of code duplication.
Comments should be comments of why, rather than how and what. The Code tells you how, and the comments should tell you why. However, most programmers do not know what a good comment is. The comments are actually duplicated with the code and meaningless.
4. XML is highly overrated
XML may be overestimated. XML is good for Web applications, but we use it in various places. It seems that we will not change it without XML.
5. Not all programmers are created equal.
These are the mistakes that junior managers love to make. They always think that when their title is the same, they think they can work, speed, and solve problems, the skills are the same. What's more, in some cases, even the worst programmers will think that it is ten times better than others.
6. "Googling it" is okay!
Google will only give you knowledge and will not give you skills. There are only "fish", no "fish", and excessive use of Google will only make you unable to do without it, and you will not think, explore, or study on your own. If KFC fast food is junk food that is not good for our health, using Google is also a fast food culture that is not good for our intellectual development.
7. If you only know one language, no matter how well you know it, you're not a great.
If you only know one language, but accurately, if you only know one type of language, such as Java, C #, PHP, and Perl, then you will be limited, only by understanding different languages and different methods of different languages can you compare them. Only by comparing them can you understand the strengths and weaknesses of different languages, it will give you a more mature point of view. In addition, it will not be the same as other programmers arguing on the internet whether Windows is good or UNIX is good, whether C is good or C ++ is good, with this effort, we can do a lot of things. The world should be different and wonderful. It is harmful to know only one side of things.
8. Your job is to put yourself out of work.
Your work should not be conservative. The idea of the church apprentice and the dead master is not only very short, but also quite brainless. Because, in the computer world, the more old technologies you master, the less useless you are, because the technology is updated too quickly. The more conservative you are to work, the more you will be unable to leave this job, and the more you will be unable to learn new things, the more you will get out. Remember: If you can't be replaced then you can't be promoted!
9. design patterns are hurting good design more than they're helping it.
Many programmers regard the design pattern as a god of God. They excessively pursue the design pattern and forget what the demand is. As a result, the whole system design is messy by the design pattern, we call this programming "Design Patterns-driven programming". As the first point of view says, if you don't know how to use your own brain to think about it, you will not be able to benefit from it, instead, they are tired.
10. Unit Testing won't help you write good code.
To be accurate, we can think of it as test-driven development. In fact, this development is to write unit test cases first. The main purpose of this development method is, to prevent you from introducing bugs due to a change, this does not allow you to write better code. This will only allow you to write code without errors. At the same time, this approach only prevents poor programmers, rather than improving the quality of programmers or code. On the contrary, unit test becomes a pretext for programmers to justify their own code.