Hello reader
Today we set out from two perspectives, to talk about how to improve the efficiency of development, the development efficiency can come from personal development efficiency and team development efficiency, throw a freelancer, any work for a company of programmers must be working in a team, so everyone will eventually translate into the personal efficiency of the efficiency of the team. How big the conversion rate is depends on how cohesive the team is.
Improve development efficiency (for teams)
The language as a first language development began to have more than two years time, relative simplicity of mainstream language, the language use is very simple, filled with many online introduction to zero basis for three days, five days Go language, in fact is, there is a language based programmers, introduction to three days is not fool, 24 hours a day should be also is not easy, However, everything has pros and cons. The advantages of being simple and easy to learn also lead to a variety of ways to achieve the project, N different types of Go language Web framework, different from Java, there are universal universal Spring Boot.
The key to improving team development efficiency lies in standards. Just like Java language, as long as you master Spring Boot, no matter which company you are in, regardless of business, you will start to take over projects quickly. This is because Spring has a set of universally applicable framework standards. For example, how to read configuration files, parameter verification, the relationship between Controller and Service, etc., we can discuss and solve problems on the same standard, which can greatly reduce communication barriers and improve development efficiency. Common coding standards, using the same set of coding standards, make the code look like it was written by the same person, and this is where Go development is lacking.
The code standards here focus on the implementation of the standard, of course the code specification is also important, uniform variable naming, indent Spaces, etc.,
By parameter calibration, stratification of the model, the actual case to explain the ORM, hope to provide readers with different solution, combined with their own experience and in the business needs to find the right its own set of development standards, the language had not Spring the unified development standards around the world, but we do team level of uniform standard, Then improve the development efficiency of the whole team.
Write good code (personal)
By looking in the company of a few years, found an interesting phenomenon, 80% of the programmer’s main job is to add and delete, namely the programmer circles is a saying: the interview made an aircraft carrier, screw, whenever there is reasonable, the essence of business is to add and delete data, move brick live in every Internet companies is inevitable; How to effectively improve the work efficiency of these 80% programmers is equivalent to improving the overall development efficiency of the whole technical department, so as to ensure the development progress of the business, reduce the work intensity of developers, and avoid the 996 work schedule, which is a problem the author has been thinking about.
Whenever a few programmers get together to discuss techniques, basic it is big data, intelligent recommendation, block chain technology on these sounds very bluffing is very tall, very few people discuss their usual do add and delete, most probably all think this is the most basic technique no technical content, but I think on the contrary, No matter how complex a project is, it starts from the first line of code, and no matter how complex a business is, it is composed of classes and methods. How to write good code is also ignored by most programmers, or the company takes the completion of the project as the criterion, the function is completed, and the code quality is secondary.
What is good code? Online design principles, design patterns, explain a lot of articles, and is seen after understand understand, feeling is very good, but when the real development of writing code, writing code or a tuo tuo, hope that through encountered in the actual case to explain in detail, understand maintainable and easy to read the code is long what kind, is how to write, Understand the evolution process of the whole code, the code quality is good, the bugs will be less, and the interaction with the test will be less, it will not be because of the previous bug and affect the progress behind, the efficiency will be naturally high.