Recently, there are a lot of demands, two are waiting for testing after development, one is ready to develop, one is in development, and one is waiting to jump the queue to join. There have been three PD quarrelling over my time next week, the last time such a scene was a lifetime ago.
So there’s a little bit of a feeling about r&d efficiency, so I’ll note that as well.
The first order is the purpose of the requirement. The value point of the purpose and whether the purpose is the means to achieve the value is very important, otherwise we will only be confused by trial and error, without a correct logical chain to promote the development of things.
The second is the evaluation, which includes the evaluation of the scope of their own research and development, and the evaluation of the collaborators. Otherwise, in the case of cognitive inconsistency between the two sides, whether both sides have wasted resources, or both sides have not done the demand delay is not a good thing.
The third order is precipitation. After making this requirement, can we do less other requirements in the future, such as the abstraction of a function, the abstraction of a field definition, and the construction of a platform? Better abstraction can help better precipitation, and better precipitation can bring more improvement of research and development efficiency.
Fourth is the test and investigation, write single test is really annoying, but do not write single test, thousands of lines of code written, there are always a few if forgotten or added! Symbol, so, to avoid frequent commit…. Single test must be completed…