Today, I finally turned it, the company asked everyone to write some of the stuff and the like. Think about it, or it is the same. Experience:
The development process loop is closely related, so it is necessary to understand the overall progress on the basis of clear and do its own work.
The development role is detailed and interactive, so pay attention to strengthen communication and communication.
The system we develop has a wide range of systems, and the content is annoying, so the volume is also very large, and it is possible to develop a small function. It is also very familiar with the needs, the system, the system, the interface.
Pay attention to new technologies in the field, if new technologies do not improve work efficiency, try to apply to development.
problem:
Personally feel that the current system should be more fully useful, which can be more flexible in future maintenance.
Another feeling is that the work interaction of the test team and the development team is not in time, a tester finds a bug, developer Debug, tester again, this cycle is relatively long, usually more than one day, if you encounter some repeated Trouble. Whether you can pass version control technology, this cycle can be shortened.
In terms of code development, I feel that the current code reuse is further strengthened. This is not only requiring to write code. To consider reuse, the key is to make it easy to tell you how you write the code after using and want to complete a feature. I think this is also a place currently worthy of improvement.
In terms of workload assessment, I think that the number of lines used as one of the standards is very unscientific. Because of usually, for the same needs, it is definitely a simple code better.
