Seven crimes of counting software R & D Efficiency

I wrote two articles before , Respectively introduced “ Negative list of software R & D Efficiency ”、“ Ten wastes of software research and development ”, Today is a summary of the negative aspects of software R & D effectiveness , Dig out the reasons behind . In essence , Are human weaknesses , These weaknesses become the resistance of software R & D efficiency , Even drag down the software R & D efficiency .

A crime ： selfish

• For their own promotion or protect their position , I hope my team can expand rapidly , The more people you manage, the better , Regardless of low performance ; Discuss in detail , You can refer to an article written before ： Many R & D managers do not want to improve R & D efficiency , That's the big question ！

• “ Everyone sweeps the snow in front of the door , Don't worry about the frost on others' tiles ”, Some managers , Only pay attention to one third of one mu of land , Regardless of the overall interests , Local efficiency seems good , But the overall efficiency does not go , There may even be serious conflicts ,1+1<2, instead of 1+1>2;

• Waste of resources ： I have good resources （ Including human resources ）、 Good learning materials are your own , And will not take the initiative to shout to everyone ： There are good resources here 、 Good material , Do you want to use ？

• Lack of sharing spirit . Make a good design 、 Write good code , The experience and inspiration gained from it are not willing to share , I don't even want my colleagues to know .

Two sins ： Face saving 、 Vanity

• Image project ： Willing to spend a lot of money to build a big screen , Present some beautiful figures , Such as 100% Automated test rate 、100% Build success rate 、 Daily release 10 A version 、 The average release is as high as 10 User stories ...... But the quality of delivery ？ Is it what users want ？ How satisfied are users ？ Some key data are not available ; for example 100% Automated test rate , However, the investment cost of actual testing remains high , The efficiency is not high .

• Pursue good-looking indicators and conducive to their own interpretation ： Even the same data , See how we interpret it , If only for the sake of looking good , There will be a good interpretation . And you can measure what you want , If you just want to look good , You will measure what is good for you , Even we cannot underestimate what people are pursuing “ Good looking indicators ” Upper “ creativity ”. But actually , We often want data to help us find problems , and “ Face saving ” contrary .

• I like large and comprehensive platforms （ Including development platform 、 Efficiency platform 、 Measurement platform 、 Test platform ）, Instead of specialized and sophisticated tools , Cause trouble in using the platform 、 Low circulation efficiency ;

• Some engineering practices are also for appearance , Often reduced to a form or just a slogan , Even make up for the number , Include performance measures 、 unit testing 、 automated testing , It's a beautiful demonstration , But the actual project is a mess , And their hearts do not necessarily recognize its value . Some documents are beautifully made , But to cope with some so-called international certification 、 Internal review and make-up afterwards , So the efficiency is not improved in essence , On the contrary, it seriously slows down the efficiency .

Three sins ： desire

• Desire is never enough , To fill some people's desires , Software development often comes at a high price .

• Such as possessiveness , Some jobs （ Including jobs , Like the development manager 、 Test manager, etc ） Not for him , But because it came early , Occupy the right time and place , But he was reluctant to let it out , Hindering R & D change （ Such as the integration of development and testing ）.

• Yes Some jobs are all about satisfying your desire for money , for example , The wheel is built repeatedly for the sake of one's own achievements , In order to get a raise and a bonus , In fact, there are ready-made and easy-to-use tools on the market （ Leaders may not know ）, The wheels made by ourselves are not as easy to use as open source tools （ Leaders may not know ）;

Four crimes ： be fond of the new and tired of the old

• Like to write new code , Develop new features , Code keeps accumulating , But never optimize , This leads to a bloated 、 Fragile code base , Difficult to maintain effectively .

• Pursue new technology 、 New programming language 、 New design patterns , Keep trying new things , Constantly in different technologies 、 Switch between language and mode , How much code and time is wasted , reckless disregard ; And the new technology is not mature , Make the quality of the system unstable , It's even bad , Lead to a lot of rework .

Five sins ： pride 、 Blind arrogance

• Blindly infatuated with their own tools , Even if it's hard to use , Also not willing to abandon , As a result, bad money will eliminate good money ;

• I always feel that my design or code is good , The tester found the defect , Don't doubt your code , Instead, they question the tester ： Are you mistaken ？ Thus affecting communication and collaboration , Reduce R & D efficiency .

Six sins ： be crazy about foreign things and obsequious to foreigners

• si ： Regardless of the context , As long as it is a big European and American factory （ Such as Google、Apple、Amazon Other large factories ） Practice is good practice , Compared with the . Some R & D teams of small and medium-sized enterprises do not know their own teams , Don't know your environment , Copy big factories in Europe and America （ Even large domestic factories ） Practice , Cause acclimatization , Efficiency declines instead of increases . Little imagine , oranges change with their environment . Just as the same medicine given to elephants can cure diseases , And giving you food could kill you . Die without change , But change is wrong , Will die faster . Change is needed , We must adjust measures to local conditions . Others' experience can be referred to , Be clear about the context , Then make adjustments . The road that suits oneself must come out by oneself after all , Pulling up seedlings and encouraging others can only be a flash in the pan .

• Don't know, pretend to know , Blindly follow suit , Do not understand the origin of a certain practice , What is the problem to be solved , As long as people say yes , As long as everyone is using , Just use it , It is also possible to die .

Seven deadly SINS ： lazy

• Laziness is the root of all evil , It can be seen that laziness brings great harm .

•   Be lazy if you can . Writing code without validating input is a common mistake , disease enters by the mouth , Many common security vulnerabilities （ Such as buffer overflow 、SQL Injection attack, etc ）、 System crash due to null pointer , It's all because of “ No validation input ”. The code is missing a comment line , Poor code readability , Unit tests can be done without , Code review goes through the motions ,... It's all caused by laziness .

Through this article and the following 4 An article , We have a thorough understanding of the nature of software R & D and the negative aspects of software R & D effectiveness , Next week we start thinking about how to overcome these problems 、 Put software development on the right track , How to continuously improve efficiency ...

• The underlying logic of software R & D efficiency

• Hit the soul ： The first principles of software development and 10 Double efficiency

• Negative list of software R & D Efficiency ： Which is the number one enemy ？

• Ten wastes of software research and development ： The other side of R & D effectiveness