Cultivation of excellent ASP. NET programmers and asp.net programmers

Cultivation of excellent ASP. NET programmers and asp.net programmers

Junior programmers or inexperienced programmers often only realize that their programs are written to computers, and do not care that the programs are actually written to people, or are not fully intended.

The programs written to machines often seek to run correctly and meet the requirements of execution efficiency. But is the programmer's task simply to convert the business logic into computer languages that can be compiled by machines?

In fact, the program first (note, first) is written to people. First, the program is written to the person who reads the code. Second, the program is written to the user. Only by understanding this can we understand why code standards are required for writing programs, why various documents are required, why is there a good name when writing subprograms, why is there a hierarchy, and why we need to learn the design pattern, why do we need to write test cases, why do we need to push button placement, why do we need to write Web interfaces according to XHTML standards, and why AJAX... ... With this understanding, we can do the above things better.

Everyone is saying "Details determine success or failure", and everyone knows to pay attention to details. Why are we talking about details? Some people can beat their opponents through details, while others don't even know where the details are. This is where the level is. We need to be prepared: the details will appear in front of you without a shout. Perceiving details is a process that requires continuous learning and practice, or even guidance from others. This process is long and short. It depends on the individual's learning ability and comprehension ability. But at the very least, we must first have a direction. Looking for the details of a program, the direction is to "write a program for people". When you design, write code, and play with the interface, remember this point all the time, you can naturally see a lot of details.

"Internal and external repair"

Martial arts film experts often use the Qimen method to rapidly increase internal force and become masters. However, if we do a program, we must become a master and "both inside and outside" can get twice the result with half the effort. It refers to requirements, design ideas, design patterns, and so on. In addition, it refers to the code writing specifications and the rigor of the interface.

When we look at martial arts, we are much more inside and outside, which is very obvious. The comparison between the number of books in the reading shop that write design patterns and the number of books that guide code specifications is a good proof. However, even if you have a set of design patterns, you will still be stuck in a quagmire after a year or two if the classes you write do not show your mind for a long time.

For another example, some people claim to be ASP. NET programmers, and the background code he wrote is also clear and well-organized. However, the structure and performance of the interface are mixed, and a lot of garbage code automatically generated by the IDE is filled, the text box and button of the ticket should be put in a place that nobody can think of. user operations should not be performed by users, and operations cannot be completed in steps that can be completed in one step ...... Obviously, it is impossible for him to make a successful product. Maybe he also knows that the interface should be reasonable, but because he does not do external work, he thinks that I am engaged in advanced technologies such as. NET. Isn't it worth it if I want to learn about HTML, JavaScript, and CSS? In fact, people who have carefully studied HTML and JavaScript technologies will find that using these technologies is more popular. NET and Java are more challenging, and after you obtain the ability to directly operate user interface elements, the previous situations where the Interface Effects and interface functions are powerless will not be returned, this is very painful!

How to Learn ASP. NET http://hovertree.com/menu/aspnet/

To become an excellent ASP. NET programmers should not only master. NET Framework, understanding ASP. NET principle, and must be familiar with DHTML, and even understand the differences between various browsers, so do ASP. NET programmers are a very challenging job. So how to learn ASP. NET and eventually become an excellent ASP. NET programmer?

I think there are two steps: first, familiarize yourself with the usage of various ASP. NET standard controls and understand the working principles of ASP. NET. Then, expand your knowledge and skills in the "Inside" and "outside" directions.

With the help of excellent IDE such as Visual Studio. NET, it is easier to use various ASP. NET controls to master the basic working principles of ASP. NET. If you can use a few simple projects to practice complex data binding controls such as DataGrid and DataList, you should be familiar with ASP. NET.

Then we can move in two advanced directions. It is mandatory to deeply understand the object-oriented programming ideology, and then the understanding of various B/S frameworks (such as MVC, finally, it is the concept and technology of software engineering, such as the design model. "External repair" is more important to practice. First, pay attention to the implementation of some logic that can be implemented on the client using DHTML on the client, in order to master the methods that combine the server and client technology, and deepen the understanding of html dom objects, familiar with common JavaScript skills. Further, we will plan, design, and implement the separation of the structure, data, and performance of the Web interface.

It seems that learning ASP. NET is not very difficult. Pay attention to "writing programs for people" and "both inside and outside", and naturally make qualified applications.

Recommended: http://www.cnblogs.com/roucheng/p/texiao.html