Ext: 10 Good programming ideas. (Source: Cool Shell –coolshell.cn)

There's a post on stack overflow, "What's your most controversial programming opinion?" translated into Chinese is " What do you think is the most controversial programming idea?" However, in more than 400 main huitie, as well as thousands of huitie, it seems that it is not very controversial, but rather quite enlightened, listed below, and through my own experience and understanding to play some, I hope to help you.

1) The only ' best practice ' should be using all the ' use Your Brain '.

The only "best practice" is not to use a variety of design methods, patterns, frameworks that have been summed up by predecessors, the famous methods, patterns, frameworks, and the number of people who agree with them, do not mean that they are right for you, you should use your brain more independently and think about the methods, patterns, The reason for the emergence of the framework and the ideas and ideas behind it is "best practice". In fact, the so-called "best practice" is nothing more than limiting the destructive power of bad handlers.

2) Programmers who don ' t code in their spare time to fun would never become as good as those that does.

If you do not feel a joy of programming, not in your free time to live in a way of entertainment, whether it is programming, or sports, or travel, then you are only dealing with your work, all the time in the program heap, so down, even if you are a very smart, very talented person, You're not going to be a good programmer either, or you'll only be a nerd in technology all day. Of course, this view is controversial, the gap between enthusiasm and ability is also great. But we can draw a positive view from it.

3) M OST comments in code is in fact a pernicious form of code duplication.

The comment should be comment why, not how and what, see the 10 things that annoy a programmer, the code tells you how, and the comment should tell you why. But most programs don't know what a good comment is, and those annotations are actually repetitive and meaningless.

4) XML is highly overrated

The XML may be overvalued. XML is good for applications on the web, but we use it in a variety of places, as if there is no XML, and we are not programmed.

5) Not all programmers is created equal

This is the junior manager or the process of love, they always think, Developera = = Developerb, as long as their title, they think their ability, work speed, problem-solving methods, skills and so on are the same. Oh. What's more, at some point, even the worst programmers, they think they're 10 times times more powerful than others, and that's modern SB management.

6) "Googling it" is okay!

Google will only give you knowledge and will not teach you skills. There is only "fish", there is no "fishing", excessive use of Google, will only make you more and more inseparable from him, you are more and more to go to tell you the answer, and you more and more do not think yourself, to explore, to research. If KFC fast food is junk food is not good for our health, then using Google also a fast food culture is not good for our intellectual development.

7) If you are only know one language, no matter how well do you know it, your ' re not a great programmer.

If you only know one language, say exactly, if you only know a class of words, such as Java and c#,php and Perl, then you will be limited, only to understand a variety of languages, understand the different ways of different languages, you will have a comparison, only the comparison, you will understand the strengths and weaknesses of various languages , will let you have a more mature point of view, and not all day and other programs in the online bickering argument is Windows good or Unix good, is C good or C + + good, have this time to do a lot of things. The world is wonderful because it is different, only know the side of things is harmful.

8) Your job is the put yourself out of the work.

Your work is not conservative, the idea that the Church apprentice, starving Master, is not only very short-sighted, but also quite brain-crippled. Because, in the computer world, the more you master the more old technology, the more useless you will be, because the technology updates too quickly. The more conservative you are with the job, the more you can get away from it, the less you will be able to learn new things, the more you get out. Remember: If you can ' t is replaced then you can ' t be promoted!

9)Design patterns is hurting good Design more than they ' re helping it.

Many programmers put the design patterns as the gods, they are too much in the pursuit of design patterns and even forget what the demand is, the whole system design is a chaotic design pattern, we call this programming "design mode-driven programming", as the 1th said, if you do not know how to think with your own brain, know it, If you do not know why, then you not only get the benefits, but by its tired.

Ten) Unit testing won ' t help you write good code

To be precise, we can think of this as test-driven development, in fact, this development is the first to write the unit test case, the main purpose of this development method is to prevent you from introducing bugs because of a change, but this will not allow you to write better code. This will only let you write code that doesn't go wrong. With the 1th, this approach is just to prevent bad programmers, not to make programmers or code quality more progress. Instead, the unit test is an excuse for programmers to justify their own code.

Finally, by the way, to the agile company before the interview, found that some of the company's technical personnel poisoning is not shallow, specifically in the above 1) 9) 10) point of view.

(reprint: Author and source cool shell –coolshell.cn)

Ext: 10 Good programming ideas. (Source: Cool Shell –coolshell.cn)