. NET Software engineer Career Planning __.net

When interviewing some new programmers, ask him why he chose . NET Software engineer 's direction, often hear some such answer: Remember once my teacher told us that when you do not know how to develop language and tools to choose, then you just follow Microsoft to go. So in the end he chose. NET software engineer career planning.

I think we've all had a similar experience. After several years, some people are. NET software engineer has become an expert in some aspects, some people proficient in database, some people proficient in web interface design, some people proficient in the system architecture. There are others who will, but no one is proficient at all. There are others, of course, who have no choice. NET software engineers, who chose Java, after a few years, they said: Java program systems are more stable than. NET systems. Since everyone is a. NET camp, for the moment they are not discussed, the following is a description of. NET Software engineer career planning.

1. Do not waver after choosing research direction

The question of whether. NET or Java is good, I have always said: they are all good, they are excellent tools in the field of software development, they can make a very good system. The standard for evaluating a system's good and bad is not in developing the language, but in the system itself, and more in the developer of the system-the programmer itself. As long as you are a good programmer, you can use the development language you are good at developing a high quality system, regardless of whether the development language is. NET or java. And if you wander over and over to study who they are better at, or even keep shifting between them, you will lose valuable time.

2. Narrow the scope of the study as far as possible

. NET is just a general direction, you should try to narrow your research, such as focus on the database, focus on XML, focus on Ajax, as long as you focus on any area of in-depth research, when you become an expert, will not worry about food. Conversely, if you do everything and don't have the same real mastery, then you can always be a regular programmer.

3. Find the right way to get started

No matter what you do, the method is very important. Especially when it comes to getting started. The right way to get started will greatly speed up your learning process. Understanding the language itself and the prerequisite technology is the first thing to do, such as you choose C # Direction of ASP.net, then you must first learn C # basic grammar, and asp.net basic knowledge, and actually write a small program to test the results of your study. As soon as you learn the basic grammar, find ASP.net's official introductory guide. One of the things that Microsoft does well is that his help system is doing well. Newcomers are easy to get started, it is recommended to start with the introductory tutorial, this thing is on your machine, in the Framework SDK menu. It is highly recommended to learn all this tutorial.

4. Look at other people's results (source code)

This is important, and if you are a new member of a team, it will be a great way to read the code they write, because those are successful code experiences. If you have not joined the team, is self-study, then find a good learning site, more to see the source code is also a good way. Another highly recommended approach: A closer look at Microsoft's. NET Starterkit, which I personally think is the biggest gain in the. NET Introductory learning journey.

5. Dare to accept New Project challenge, Dare to try

Take the initiative to undertake the development task of the company, dare to try your latest research in the project will be very helpful to your own technical level improvement. I remember when I was doing a platform project has such an experience, before the company developed most of the project in the original technology accumulated under the framework to do the development, then I was also learning asp.net, but that project I was the main programmer, so in the development of a great autonomy. So when I was 1.0, I tried to save all the user stories in the Web server XML file, rather than in the database as a traditional project, to reduce data transfer between the Web server and the DB server. As a result, the 1.0 system actually achieves my goal, although as the volume of data increases, it eventually leads to Io bottlenecks. But through the subsequent optimization of the IO bottleneck, I learned a lot in file system, server process, XML application, code specification and performance optimization, if the original mode of writing procedures, will miss the opportunity to learn this knowledge.

6. Constantly overthrow themselves and dare to reconstruct

This is the requirements of the quality of the program, I think only constantly optimize and transform their own program code, can finally write high-quality procedures, to make high-quality systems, and ultimately to improve their technical level. Usually I will implement a function of the amount of code as a measure of code quality standards, the less the code, the more streamlined, while also having good readability, the more ideal. Refactoring requires several prerequisites: first, the time allowed for the project, and then the fact that better code organization logic is found, such as a good structure pattern, a more rational way of object-oriented invocation, and so on. Just find a better solution, then bravely overthrow the original program framework, refactoring it, after constantly refactoring, one day you go back to look at the program you wrote before will have a sigh: wow, how before my program written so rotten AH.

7. Keep up with the pace of technical updates

Software Technology Update speed sometimes really depressing, often hear people say, Just learned. net1.0, immediately out of 1.1, 1.1 just finished one or two projects, another 2.0, with 2.0 less than a year has been out of 3.5, but the reality is that, you have to keep up with the footsteps, when using asp.net, you can no longer like the previous use of ASP to write programs, when used. net2.0, you have to Dare to use Masterpage,skin to replace the original UserControl mode, the original website skin implementation mode. Now that you're out of 3.5, you have to learn vs2008 immediately and learn about Silverlight. Only with the pace of technology updates, you will always maintain their technological leadership.

The above points . NET Software engineer Career Planning recommendations, I hope to give some of the newly added. NET programmers some reference.