How to improve development efficiency

Document directory

• Tools
• Code Accumulation
• Code Quality
• Business knowledge learning

It takes up to five days to complete a task. If you have used six days, it can be said that the development efficiency is low, or the same task has taken six days, however, it takes only four days for your colleagues. It can be said that your development efficiency is not high and there are many factors that affect the development efficiency, the following is my personal understanding of how to improve development efficiency.

Tools

As the saying goes, to do a good job, you must first sharpen the tool. Using handy tools will inevitably improve the development efficiency. For the development of Microsoft platform, VS is indispensable. For VS itself, in addition to common functions, some common shortcut keys must be used skillfully. For example, the following are some useful shortcut keys:

• Note: Ctrl + K + C
• Uncomment: Ctrl + K + U
• Full Screen: Shift + Alt + Ente
• Set the tag: CTRL + K, CTRL + K
• Next and last labels: CTRL + K, CTRL + P, CTRL + K, CTRL + P
• List Members: Ctrl + J
• Display parameter information: Ctrl + Shift + Space
• Go to the definition and return: Ctrl +-

The Skillful Use of shortcuts greatly improves the speed of code writing and the speed of code tracking. Sometimes the functions of the development tool are limited. This requires the use of plug-ins to provide rich functions. We recommend two plug-ins: ReSharper in VS and SQL prompt5 in SqlServer, reSharper is a powerful VS plug-in, but it will slow down the speed of VS, and it depends on how to weigh it, I have briefly introduced the powerful VS plug-in-Resharper in my previous blog post. SQL prompt5 is a SqlServer plug-in with powerful functions and a strong smart prompting function. The SQL Search function provides quick Search for database objects and code snippets, I have also introduced SQL Prompt5 in my previous blog article ". In addition to VS and SqlServer, which we can't do without every day, there are also some auxiliary development tools that can help us improve efficiency. I often use the following:

• SqlDbx: A very small database management tool. It is very powerful and supports multiple databases. It often uses smart prompts, script generation, and other functions, but it also has shortcomings, not very good support for Chinese characters;
• Aptana: this tool can be said to be a powerful tool for Web development. I sometimes use this tool for JS writing. The highlight of this tool is that it intelligently prompts whether different browsers support it;
• Free Javascript Editor: You can easily write and run some simple HTML and JS Code. You can directly select JS code snippets for execution and debug Javascript.

Some other tools are also very useful. For example, I often use Total Commander and Everything in my daily work:

• Total Commander: a tool used to replace resource manager. It supports multiple tags and allows you to conveniently operate files;
• Everything: a search tool that is extremely fast. We have also introduced the software recommendation: Everything, a disk search software.

Code Accumulation

Software companies of a certain scale have their own development frameworks. These frameworks are the product of years of accumulation to improve development efficiency, as a developer, you should also have your own precipitation for some common code, not only by yourself, but also by sharing with each other in the group, you can record the accumulated code based on your preferences, such as Notepad, Word, Excel, and OneNote. The precipitated code can also be managed using the code snippet function of VS, which is well supported in VS2010. The plug-in SQL Prompt5 mentioned above also provides the code snippet function in the database. VS provides many ready-made code snippets. the most convenient way to use custom code snippets is to use the code snippet production tool. Click here to download the tool, of course, you can also create a code snippet file and import it in VS. The code snippet file is actually an xml file with the suffix snippet.

Code Quality

If the code quality is good, fewer bugs will be generated, and less interaction with the test will be achieved. In this way, the subsequent progress will not be affected because of the previous bugs, and the efficiency will naturally be higher. Code quality can be divided into three aspects: 1. The Code has fewer errors and can run normally;

• Active learning to improve programming skills;
• Keep in mind the normative principles that often lead to low-level errors;
• After a task is completed, it must be fully self-tested.

2. The code is highly efficient and can run efficiently in big data and high concurrency;

• High-performance development starts from scratch. Every detail is ignored. A small detail may be a performance bottleneck;
• We need to have the habit of refactoring code. Good code is reconstructed, and high-performance code is also reconstructed;
• I want to learn more about the principles. I need to know more about the principles. I have a solid foundation, and I will know how to optimize some performance problems;
• I have translated several blog posts about C # code simplification. For more information, see C #/Net code streamlining optimization (1) and C #/Net code streamlining optimization (2) and C #/Net code streamlining optimization skills (3)

3. The final running result of the Code must be consistent with the customer's requirements;

• Communicate your understanding with the requirement analysis to see if an agreement can be reached. If you communicate with the customer directly, you can first make a small Demo and then present it to the customer, continuous improvement based on feedback;
• In the process of doing so, if you have any questions, you must communicate with your needs or customers. Do not write code based on your own ideas;
• When necessary, we can guide customers. Our main goal is to help customers solve problems in the most effective way. We cannot blindly follow customers' requirements. Sometimes customers say they need a pair of rain boots, an umbrella may solve the problem. Similarly, for the documents written in requirement analysis, development also needs to be challenged.

Business knowledge learning

No system can avoid business background. A good understanding of business knowledge can help us better understand what we are doing. Many developers may only like to study technology, and often have no interest in the business. After the code is written, they may not know how to use the modules, in this way, the quality of the written code can be imagined.

• Learning business may be boring, but it is a permanent task. Therefore, whether you are interested or not, you should stick to your head;
• An interest group can be set up in the group to explore ways to learn and share their learning content. The key is to build an atmosphere in the group;
• If you want to communicate directly with the customer, you need to use the language that the customer can understand, or use some small demos. Otherwise, when the Development Term hits the field term, it may be playing the piano.

In short, as a developer, you should always think about how to improve development efficiency. The improvement of development efficiency is the beginning of a virtuous circle in your work. If you have good methods and suggestions, please share them with us.