In this world, millions of people are interested in software development, they have many names, such as: Software Engineer (Software Engineer), programmer (Programmer), encoding human (Coder), the developer (Developer). Over time, these people may be able to become a good coders, they will be very familiar with how to use computer language to accomplish their work. However, if you want to become a good programmer, you may need a few things you need to pay attention, if you make the following ten entries become your habit, then you can truly claim to be a good programmer.
-
Life-long learning. Even if you have more than 10 years of experience programmer, you have to be hard to learn, because you are in a creative field full of computers, every day there are a lot of new things appear. You need to keep pace. You need to learn a new programming language, as well as developing understanding of programming languages, as well as some programming framework. Need to go read some of the industry news, and some popular community to participate in online discussions, so that you can understand trends and understand the whole software development. In China, some well-known communities such as: CSDN, ITPUB, CHINAUINX and so on, in a foreign country, it is recommended that you regularly on a variety of polymerization on digg.com to see the BLOG.
-
Multilingual. Programming language always has the most suitable areas. When you are faced with a problem to be solved, you need to find the most suitable language to solve these problems. For example, if you need performance, you may C / C ++ is the first choice, if you need cross-platform, probably Java is the first choice, if you want to write the development program on a Web, then PHP, ASP, Ajax, JSP may be your choice If you want to deal with some text and interact with other applications, it may Perl, Python would be the best. So, take some time to explore what you and others familiar with the programming language that allows your eyes widened, because you are armed better, you think there is more comprehensive, which is good for themselves and their projects will help.
-
Rational face different operating systems or technology. Programmers are always have their minds unparalleled technology and operating systems, and some people like Ubuntu, some people like Debian, there's people like Windows, and FreeBSD, MacOSX or Solaris and so on. . Only part of good programmers know that different operating systems advantages and strengths and weaknesses, so that when the system selection, in order to be truly objective and impartial, and not let emotions affect their own. Similarly, the language is the same, there are too many programmers always like to dwell on the language of comparison, such as: Java and Perl. Which just is not controversial debut programmers go a similar subject? For example, VC ++ and Delphi, and so on. Debate these things can only show their superficial and Fuzao. Excellent program and will not be attached to these, but be able to rational analysis and management face carefully, so as to objectively make the right choice.
-
Do not box yourself in a single development environment. Again, as noted above, each programmer has their own love of loyalty tools and techniques, some like the old (for example, I like Vi editing program), while others like the new, such as Emacs or gedit and so on. Some prefer to use the same as the VC ++ debugger GUI, but I prefer the command line aspects of GDB debuggers. Etc., etc. Programmers debate on what kind of tools used there? Everywhere ah. What kind of tools would have does not matter, as long as you can better achieve your goals faster. But one thing is good programmer should know - that should go to try another work environment. There is no comparison, you never know who is good and who is bad, you never know what you do not know.
-
Use version management tools to manage your code. Do not tell me you do not know the source code version management, and if your team does not develop the source code version management system, I want to tell you that your software development is still in the Stone Age. Quickly use a layout of this management tool bar. CVS is a version of the tool looks bland, but it is the most widely used version control system, Subversion is an upgraded version of CVS, which is beginning to take over the CVS territory. Git is a different version management tools. There Visual SourceSafe and so on. What kind of version management tools rely on your team size and geographic distribution, you probably are not using the most efficient or the most efficient tool to manage your source code. But a good programmer will always use a source code version management tools to manage their own code. If you want me to recommend one, I recommend that you use the open source Subversion.
-
It is a good team member. Unless you like to solo, unless you are a lone hero. But I want to tell you, today, may not have a mature software is that you can do to a person, you may be on your team to get the most cattle big, but that does not mean you're a good team. Your ability to put a team can only applied to start. You polite in your team members and exchange it? How often do you communicate with them, and we all like to discuss with you the problem? Think about it a football team, you are a member of this team do good? When people see you on the court running, when you see someone passing and steals the ball and your members to members because your actions are encouraged by it?
-
Put your work into the document. This of course includes entry to write comments in the code, but that is just not enough, you also need to do more. Good comment style code is the basis of a document, he can make you and your team to easily understand your intentions and ideas. Write down the document, and not just afraid we forgot the idea was, and still off-line exchange of a team, it is a method of knowledge transfer. Next record everything you know would be a good habit. Because, I believe you do not want others to always be at your busiest time to interrupt you to ask questions, or if you received the company's phone on vacation to ask your questions. And if you always keep his things, the result can only be a long time to make yourself deep in this thing, and you can not do this even more things. It includes an upward promotion. You might think that the "church master apprentice can starve to death," but I tell you, you will make you lose more conservative and better things, please believe me, I am not here sensational.
-
Note backup and security. You might think this is a "nonsense", you already understand the importance of backup. However, I want to propose here, something is missing a part of our life, and you always will throw things, you can never avoid this. For example: your laptop is stolen, your hard disk is damaged, your computer a virus, your system was ***, and even the whole building burned, and so on, and so on. So, make a backup job is very, very important thing, the hard disk is not credible, so the regular burn discs or tapes might be a good way to network is not credible, so be careful virus and ***, not only use the security policy aspects of the software, you need a sound management regime. In addition, try to keep your data in different places, and do a good job on a regular basis (daily, weekly, monthly) backup strategy.
-
Designed to be flexible enough. Maybe you need only ask you realize what a dead, but you as a good program, you should always consider whether something in the dead can have flexible side, such as the number of parameters that can be configured to become, the Some common things form your library for later reuse, whether to provide functional plug terms? Do you want to random combinations of modules like building blocks to? If you have modified, then your design is able to immediately cope? Of course, the flexible design may not want you to reinvent the wheel, you should be standardized as much as possible of things. The so-called spirit of the design is to make words make more things to consider than the demand, the demand for this type of problem are taken into account, rather than just processing requirements stated in that particular thing. For example, you need the required screen resolution is 800 × 600, so you can design flexibility than other resolution? Programming always we need to deal with different environments, as well as future trends. We need a dynamic vision to think, rather than disregard the changing circumstances. Maybe one day, you write today will program ported to other environments go, at that time you can really understand what is the flexible design.
- Do not shoot yourself in the foot. Programmers always have a bad habit, that is, always wanted to get the job done in my own hands. Yet this is often what has been willing to violate. Want to do more faster, the more vulnerable, the more want to do quickly, is easy to miss the more the problem, ultimately, to change the program changed over the last press played a gourd dipper, it takes time and effort but the final More. Haste makes waste. Good programmers to spend more time in front of the habit is to make more some research, experiment with different solutions, if time permits, a good habit is, every four hours of programming, an hour's rest, then another 4 hours of coding. Of course, this varies, but its purpose is to make you always look back, let you think about three questions: 1) whether to do so is right? 2) whether to do so taking into account all of the circumstances? 3) Is there a better way? I think it over again, often look back at the road traveled, often sum up the past things, you will have a great help.