. NET programmer how to grow up quickly I see

Transferred from: http://www.cnblogs.com/kangshif/archive/2008/07/24/starter.html

When interviewing some new programmers, when asked why he chose. NET direction, often hear some of the answers: Remember once my teacher said to us, when you are in the development of the language

and tools do not know how to choose the time, then you just have to follow Microsoft to go. So eventually he chose. Net. I think we all had a similar experience.

After several years, some people become experts in some aspects of. NET, some are proficient in database, some are proficient in web interface design, others are proficient in the system architecture.

Some people are everything, but in either case they are not proficient. Of course there are others who have not chosen. NET, they chose Java, and after a few years they

The Java program system is more stable than the. NET system. Since everyone is the. NET camp, let's not discuss them for the moment.

Combine your own personal experience with some quick growth tips for preparing to become a. NET programmer and a newcomer who has become a. NET programmer

1. Do not waver after selecting the research direction

The good thing about. NET or Java is that I always have the view that they are all good, they are great tools in the field of software development, and they can make very good systems. Reviews

A good and bad standard of a system is not the development of language, but the system itself, more of the developer of the system-the programmer itself. As long as you are an excellent program

You can develop a high-quality system in a language that you are good at, regardless of whether the development language is. NET or Java. And if you hover over to study them to

At the end of a better time, even constantly in between the two, you lose will be precious time.

2. Minimizing the scope of the study

. NET is just a general direction, you should try to narrow your scope of research, such as focus on the database, focus on XML, focus on Ajax, as long as you focus on any one region

In-depth study, when you become an expert, you will not worry about food. Conversely if you have everything, but not the same real mastery, then you can always be a normal 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 is to speed up your learning process. Understanding the language itself and the premise technology is the first thing to do

, such as the one you chose for the C # direction, you must first learn C # basic syntax, and the basic knowledge of ASP, and actually write a small program to test the results of your studies. When learning

Find the official introductory Guide to ASP immediately after basic syntax. One of the things Microsoft does well is that his help system is doing well. Newcomers are easy to get started and suggest first

Starting with the examples and QuickStart tutorials, this thing is on your machine, in the menu of the Framework SDK. It is highly recommended to learn all about this tutorial.

4. See the results of others (source code)
This is important, if you are a new member of a team, then looking at their written code will be a very good way to learn because those are successful code experiences. If

You have not joined the team, is self-study, then find a good learning site, more look at the above source code is also a good way (here friendship recommended my own collation of a generation

Code Learning Website: http://www.study-code.com, seems a bit of suspicion of advertising ^-^). Another highly recommended approach: A closer look at Microsoft's. NET Starter

Kit, personally, believes this is the biggest gain in. NET introductory learning.

5. Dare to accept the new project Challenge, Dare to try
Take the initiative to undertake the company's development tasks, dare to try your latest research results in the project will be of great help to your own technical level improvement. Remember when I was doing a

Build station platform project has had such experience, before the company developed projects mostly in the original technology accumulation under the molding framework for development, then I was learning

ASP. NET, but I'm the master programmer for that project, so I have a lot of autonomy in development. So when I was 1.0 I tried to save all the user articles in the Web server's XML text

In the database, rather than as a traditional project, in order to reduce the data transfer between the Web server and the DB server. Results 1.0 The actual runtime of the system does

It was my goal, though, as the amount of data increased, it eventually led to an IO bottleneck. But through the subsequent optimization of the IO bottleneck, I am in the file system, the server into the

, XML applications, code specifications, and performance optimizations, and if you write a program in the original mode, you will miss a good chance to learn this knowledge.

6. Constantly overthrow oneself, dare to reconstruct
This is the quality of the program requirements, I think only to constantly optimize and transform their own program code, in order to finally write high-quality programs, to make high-quality systems, and ultimately

Make your own skill level to improve. Usually I will implement a function of the code as a measure of code quality standards, the less code, the more streamlined, but also has a good

Reading, the more ideal. Refactoring requires several prerequisites: first, project time permitting, and then really finding better code organization logic, such as a good structural pattern, more

Reasonable object-oriented invocation method and so on. If we find a better solution, then bravely overthrow the original framework of the program, reconstruct it, after continuous reconstruction, there is a

God, you go back to look at the program you wrote before there will be a sigh: Wow, how my program was written so Rotten AH:)

7. Keep up with the pace of technology updates
Software Technology Update speed sometimes really makes people very depressed, often listen to people say, just learn. net1.0, immediately out of 1.1, 1.1 just completed one or two projects, and out of 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 pace, when using ASP, you can no longer like the previous use of ASP to write programs

, when using. net2.0, you should dare to use Masterpage,skin to replace the original UserControl mode, the original website skin implementation mode. And now out

3.5, you must learn vs2008 immediately and learn Silverlight. Only by keeping up with the pace of technical updates, you will always maintain your technical leadership position.

The above suggestions, I hope to give some of the newly added. NET programmers some reference.

. NET programmer how to grow up quickly I see