What are the minimum requirements for C# programmers?

1: Team spirit and collaboration ability

Taking this as a basic quality is not unimportant. On the contrary, it is the most basic and most important thing that programmers should have. The foundation for settling down and establishing a life. Anyone who calls high-level programmers loners is talking nonsense. The power of any individual is limited. Even a genius like Linus needs to form a strong team to create miracles. Those who write the core for Linux all over the world It is unimaginable without the spirit of collaboration among the masters. Lone Rangers can make some money-making small software and make a small fortune, but once they enter the R&D teams of some large systems and enter commercialization and product development tasks, people who lack this quality are completely unqualified.

2: Documentation Habits

Anyone who says that high-level programmers never write documents is definitely a naive child. Good documentation is a very important link in the formal research and development process. As a code program As a programmer, it is normal to spend 30% of your working time writing technical documents, but as a senior programmer and system analyst, this ratio is much higher. Without documentation, a software system lacks vitality and will encounter great trouble in future troubleshooting, upgrades, and module reuse.

3: Standardized and standardized code writing habits

As the rules of some well-known foreign software companies, the variable naming of the code, the comment format within the code, and even the length of the indentation of nested lines There are clear regulations on the number of blank lines between functions and functions. Good writing habits not only help with code transplantation and error correction, but also facilitate collaboration between different technical personnel.

Some coding fans clamor that other people can never understand the code written by high-level programmers. This clamor only proves that they themselves are not qualified to call themselves programmers. The code has good readability, which is a basic quality requirement for programmers.

Looking at the entire Linux construction, without standardized and standardized coding habits, global R&D collaboration is absolutely unimaginable.

4: Requirements understanding ability

Programmers need to understand the requirements of a module. Many children tend to only focus on one functional requirement when writing programs. They attribute all performance indicators to the hardware and operating system. and development environment, while ignoring the performance considerations of the own code. Someone once said that writing an advertising exchange program is very simple. Such people never know how to achieve performance indicators in the case of millions or even tens of millions of accesses. , For such a programmer, if you give him Deep Blue’s system, he will not be able to achieve the parallel access capabilities of Tai Chi Chain. Among the performance requirement indicators, stability, access support capabilities, and security are all important. As a programmer, you need to evaluate the environment in which the module will operate in the system, the load pressure it will be subjected to, and various potential dangers and malicious attacks. possibility. In this regard, a mature programmer needs at least 2 to 3 years of project development and tracking experience to be able to gain experience.

5: Reusability, modular thinking ability

It is often heard that some programmers have such complaints. After writing programs for several years, they have become skilled workers and work hard every day. It is to repeatedly write some code without any new ideas. This is actually the biggest waste of Chinese software talents. Some repetitive tasks have become the main work of skilled programmers, and these are actually completely avoidable.

Reusability design and modular thinking require programmers to think more when completing any functional module or function. Don’t be limited to simple ideas for completing the current task. Think about the Whether the module can exist without this system and whether it can be directly referenced in other systems and application environments by simply modifying parameters. This can greatly avoid repetitive development work. If a software R&D unit and working group can If these issues are taken into consideration during a research and development process, programmers will not waste too much time on repetitive work, and will have more time and energy to invest in innovative code work.

Some good program module codes, even if they were written in the 1970s, can be used very well as functional modules in some systems today. But what I see now is that many small companies As soon as the software is upgraded or improved, the entire code is often rewritten, and most of the repetitive work is a waste of time and energy.

6: Testing habits

As for some commercial and formal development, full-time test engineers are indispensable, but this does not mean that there are full-time test engineers and programmers. You don’t need to conduct self-test; software development as a project, a very important feature is that the earlier the problem is discovered, the lower the cost of solving it. Programmers should carefully review each piece of code and each sub-module after completion. Through testing, some potential problems can be discovered and solved as early as possible, so as to maximize the efficiency and reliability of the overall system construction.

Testing work actually needs to consider two aspects. On the one hand, it is the test of normal calls, that is, to see whether the program can complete basic functions under normal calls. This is the most basic testing responsibility. Unfortunately, in many companies This has become the only testing task, but it is actually far from that. The second aspect is the testing of abnormal calls, such as stability testing under high pressure loads, testing under potential abnormal user input, and partial failures of the overall system. Test the affected status of the module, test the stability of the module when frequent abnormal requests block resources, etc. Of course, programmers do not need to conduct such complete tests on every piece of their code, but programmers must clearly understand the status of their code tasks in the overall project and various performance requirements, carry out relevant tests in a targeted manner and Identifying and solving problems as early as possible requires the above-mentioned requirements understanding skills.

7: The ability to learn and summarize

Programmers are a profession where talents can easily be eliminated and fall behind, because a technology may only be leading in three or two years. If programmers want to settle down and make a living, they must constantly keep up with new technologies and learn new skills.

Being good at learning is a necessary motivation for advancement in any profession. For programmers, this requirement is even higher. But you also need to find the right target for learning. Some small coding fans also talk about their learning ability. They learned asp, php, and jsp for a while. They use this as a capital to show off and blindly They chase some superficial things and nouns, do not understand communication transmission protocols when making network programs, and do not understand interrupt vector processing when making applications. Such technical personnel, no matter how many so-called new languages ??they master, will never be qualitative. improve.

Being good at summarizing is also a manifestation of learning ability. Every time you complete a research and development task or a piece of code, you should purposefully track the application status and user feedback of the program, summarize at any time, and find your own Insufficient, only by gradually improving in this way can a programmer grow up.

Even if a programmer who does not have the ability to grow appears to be a master, it is recommended not to choose him, because the time will come when he will fall behind.

People who have all the above qualities should be said to be qualified programmers. Please note that the above qualities are not determined by IQ, nor can they be learned in some university textbooks. They need to It's just the programmer's understanding of his or her work, which is a matter of consciousness.

As a senior programmer, or even a system analyst, that is, a designer of a program project, in addition to all the above qualities, you also need to have the following qualities:

First, requirements analysis capabilities

For programmers, they can complete qualified code by understanding the requirements, but for organizations and managers of R&D projects, they must not only understand customer needs, but also more Sometimes you have to formulate some requirements by yourself. Why do you say that?

Generally speaking, when conducting R&D tasks, it may be a demand put forward by customers, or it may be a demand put forward by the marketing and marketing department. At this time, for the R&D department, what they see is not a complete demand. Generally speaking, , the requirement is just some functional requirements, or more formal, it is possible to obtain a complete user view; but this is not enough, because customers have more non-technical factors, and it may be difficult for them to put forward complete and clear, or professional Specific performance requirements, but for project organizers and planners, they must be able to clearly understand the existence of these requirements and put them forward appropriately when completing the requirements analysis report. At the same time, they must be fully and clearly reflected in the design instructions so as to facilitate Programmers code without losing these principles.

Programmers must correctly understand the environment in which user needs are located and make targeted analysis of the needs. For example, if the same software is released through ASP rental and license, the performance requirements may be different. There is a difference. The former emphasizes better support capabilities and stability, while the latter may emphasize universality on various platforms and simplicity of installation and use.

Second, project design methods and process processing capabilities

Programmers must be able to master no less than two to three project design methods (such as top-down design methods , such as rapid prototyping method, etc.), and be able to select appropriate design methods for the overall design of the project based on project needs and resource allocation. Improper selection of design methods will delay the R&D cycle, waste R&D resources, and even affect R&D results.

A programmer also needs to spend a lot of time on the design and processing of flow charts. He needs to make data flow diagrams to establish a data dictionary; he needs to process logic flow diagrams to form an overall system processing flow. . A system with process problems will not become a good system no matter how beautiful the code is and how exquisite each module is. Of course, doing a good job of process analysis and choosing a good project design method requires a sufficient grasp of demand analysis capabilities.

Third, reuse design and modular decomposition capabilities

This seems to be an old tune again. Hasn’t this issue been explained in terms of basic qualities before?

As a programmer engaged in module tasks, he needs to consider the reusability of the specific functional modules he faces. As a system analyst, the problems he has to face are much more complex. The overall system needs to be decomposed into many reusable functional modules and functions according to a modular analysis capability, and an independent design requirement is formed for each module. For example, take car production. At first, each car was installed independently and each component was tailor-made. But later, it was different. With the advent of mechanized mass production, a car factory began to produce cars through assembly lines. , independent components began to have a certain degree of reusability, and later standardization became a major trend. Auto parts of different models, brands and even different manufacturers can also be easily replaced and upgraded. At this time, the efficiency of automobile production is maximized. The same is true for software engineering. In a mature software industry, in some related projects and systems, different components can be replaced at will. For example, in many desktop software of Microsoft, in many operation modules (such as opening files, saving files, etc.) etc.) are the same set of functional modules that are reused, and these interfaces are provided to desktop application developers through some class libraries for easy connection. This is an obvious evidence of reusable module design.

Decomposing a large and complex application system into a number of relatively independent, highly reusable module combinations that can complete data connection by relying only on a few parameters is an important task for senior programmers and One of the most important tasks of a system analyst is that appropriate project design methods and clear flow charts are important guarantees for achieving this goal.

Fourth, overall project evaluation capabilities

As a system designer, you must be able to start from the overall situation and have a clear understanding of the project as a whole, such as whether the company's resource allocation is reasonable and in place, For example, whether the project schedule can maximize efficiency without failing to complete the project on schedule. Evaluating the workload of the overall project and each module, evaluating the resources required for the project, and evaluating the difficulties that the project may encounter all require a lot of experience accumulation. In other words, this is a state that can only be achieved through continuous summary and accumulation. In the West, some leaders in software system design are very old, such as 4, 50, or even older. They are far less active than young people in coding, but in terms of project evaluation, they have been working for decades. The accumulation of experience is the most important and valuable wealth. China lacks such a generation of programmers. The main reason is not that programmers of that age are lacking, but that programmers of that age are basically produced by research units and are not produced by professional productized software development. They There is no way to accumulate experience in product R&D.

Fifth, team organization and management capabilities

Completing a project requires the concerted efforts of the team. As a project designer or R&D manager, you should be able to maximize the use of the team. The overall strength of technical management is different from general personnel management due to its professional nature, because some technical indicators and factors are designed in it.

The first is the quantification of work. Without quantification, it is difficult to conduct appropriate performance appraisals. Program quantification cannot be calculated simply by the number of lines of code. Therefore, technical managers are required to be able to truly evaluate a module. complexity and workload.

The second is the adjustment of the team collaboration model. Generally speaking, collaboration in program development is usually divided into groups. There are main programmer methods and democratic methods. According to the abilities of programmers, Level gap, and according to the needs of project research and development, choose the appropriate team formation method, and closely combine the responsibilities and tasks of the members, so as to maximize the efficiency of the team.

A person with high coding skills may not be a qualified project R&D director. The lack of ability in this area is often easily overlooked.

In summary, it can be seen that as a person in charge of R&D and a project designer, the qualities and abilities required are not the ability to write program codes. Of course, in general, a programmer will pass When he has reached this level of quality by constantly summarizing and improving, his code writing ability is already quite extraordinary, but please pay attention to the causal relationship here. A high-level project designer is usually already a very good code writer. , but it does not mean that a programmer with very good code can be qualified for project design work. The problem here is not a problem of IQ and textbooks, but a problem that a programmer does not realize that he should think when he accumulates experience and gradually improves. In terms of things, there is no conscious thinking about the organization and reuse design of the project, and there is no regular documentation and summary habits. If these are not changed, our qualified project designers are still very lacking.

In addition, in order to prevent boring people from taking it seriously with me, I would like to add that the goal of this article is to do commercial software projects and engineering. Programming experts from scientific research institutions, such as algorithm experts, such as image processing Experts, their job is to research topics rather than directly complete commercial software (of course it will eventually become commercial products indirectly, such as the research topics being done by Microsoft Research), so the quality they emphasize may be something else. These people (experts), It cannot be said to be a programmer, and it cannot be measured by programmer standards.

Finally, let me add something. What is the design process of a software project development? Take the usual standard design method as an example (but I like the rapid prototyping method).

The first step is market research. Technology and market must be combined to realize the greatest value.

The second step is demand analysis. This stage requires three things, user view, data dictionary and user operation manual. The user view is the page style that users of the software (including end users and administrative users) can see, which contains many operational processes and conditions. The data dictionary is something that specifies the logical relationship of data and organizes it. Once the data dictionary is completed, more than half of the database design is completed. The user operation manual is an instruction manual that specifies the operating procedures. Please note that the user operation process and user view are determined by requirements, so they should be completed before software design. Completing these provides constraints and guidelines for program development. Unfortunately, many companies do not do this. Cause and effect are reversed. If the order is not distinguished, there will often be a disconnect between development work and actual needs.

For requirements analysis, in addition to the above work, the author believes that as a project designer, a complete performance requirements specification for the project should be made, because often performance requirements can only be understood by people who understand technology, which requires technical experts and requirements parties (customers or company marketing departments) can have real communication and understanding.

The third step is the outline design, which initially divides the system functional modules and provides reasonable R&D processes and resource requirements. As a rapid prototyping method, you can enter the coding stage after completing the outline design. This method is usually used because the R&D tasks involved belong to a new field, and the technical supervisor cannot give clear detailed design instructions at first, but it does not mean that the detailed design instructions are The design specification is not important. In fact, after the rapid prototyping method completes the prototype code, based on the evaluation results and the summary of lessons learned, the detailed design steps must be re-carried out.

The fourth step is detailed design, which is an important level that tests the design thinking of technical experts. The detailed design instructions should provide the specific modules to the coders in the cleanest way (black box structure). Maximize the overall modularity of the system; a good detailed design specification can reduce the complexity of coding to a minimum. In fact, strictly speaking, the detailed design specification should define each parameter of each function in detail. Provided, from requirements analysis to outline design to completion of detailed design specifications, a software project should be said to be half completed. In other words, when a large software system is halfway completed, a line of code has not actually started yet. Those who simply understand software programmers as code writers have made a fundamental mistake.

The fifth step is coding. In the standardized R&D process, the coding work will not exceed 1/2 of the entire project process at most, usually 1/3 of the time. Chai Gong, if the design process is completed well, the coding efficiency will be greatly improved. The most important thing to be careful about is the progress coordination and collaboration between different modules when coding. Maybe a problem with a small module may affect the overall progress, causing many programs to As a result, employees were forced to stop working and wait. This problem has occurred in many research and development processes. Mutual communication and emergency solutions when coding are very important. For programmers, bugs will always exist, and you must face this problem forever. Has the famous Microsoft ever not issued a patch for three consecutive months? ? Never!

The sixth step is testing

There are many types of testing: according to the test execution method, it can be divided into internal testing and external testing; according to the testing scope, it can be divided into module testing and overall testing Joint debugging; according to the test conditions, it can be divided into normal operation test and abnormal situation test; according to the input range of the test, it can be divided into full coverage test and sampling test. The above is easy to understand and no need to explain.

In short, testing is also a very important step in project development. For a large software, external testing from 3 months to 1 year is normal, because there will always be unpredictable problems.

After completing the test, completing the acceptance and completing some final help documents, the overall project comes to an end. Of course, upgrades, repairs, etc. will be necessary in the future. As long as you are not trying to cheat money through one-shot transactions, you must Constantly track the operating status of the software and continue to patch and upgrade it until the software is completely eliminated.

Writing these steps is not a show off, because to be honest, I have a copy of "Software Engineering" in my hand. This is a required course for computer majors in college, but I know that many programmers never seem to be just They are keen on "Mastering VC in 30 Days" and the like. Some of them are from guerrilla backgrounds like me and have never formally studied this major. Others have returned these really useful things after earning enough credits. teacher.

The Internet is also very impetuous now. Some coding fans are shouting and confusing. In fact, real technical experts rarely post random posts on the Internet. People like me who don’t know the heights of the world are actually not considered What kind of expert is this? It’s just that I can’t stand this kind of misunderstanding and nonsense about technology and programmers, so I have to stand up and speak out to bring order to the chaos. I also hope that those coding fans who are still addicted to some wrong people can think about it seriously and leave. On the right path, after all, those smart minds are far from playing their due value.