On the one hand is the duration of the emergency project, on the other hand it is difficult to do all of them are companies hiring programmers elite programmers, followed by customer demand changes, business logic frequent changes also lead to instability of the system, database model change change and so more or less affected the stability of the program, coupled with the overall procedural framework is relatively complex hierarchical stringent requirements to deploy multiple computers.
After all, a software company's budget is limited, the profit margins of the project is limited, otherwise it can be a recruiting elite development program, and got some really strong technology .NET programmer salary of more than 20K of 3-5, absolutely this thing will not produce more than 1000 Bug, if there is this thing would not elite developers, and they should be written out of the program are relatively rigorous thinking, experienced, reasonable design will stand the toss, stand the customer's tortured, that otherwise would not be worth the right.
Bug of the origin of more than 1,000 (in fact, able to test out of more than 1000 Bug also need some level):
1: 200 to test out the Bug again amended (business testers entry Guangzhou, Beijing's) management system in the Bug.
2: Fast carpet-test (3 individual tests), multiple (page divided by function) Word document finishing Bug 40, a total number of more than 500 errors.
3: meeting software function of the projector, everyone exchanges to explain the function, sorted out about error 100, simple error on the amendment a good spot.
4: code quality carpet inspection, check out the error code norms about 200, some on the spot correction is good, and some written notes rectification.
Manage these multiple 1000 Bug is not so easy:
1: The more people involved in the project, we need to have good tools to manage, such as Bug management system, we use TFS to manage content.
2: We have some people to do the test in Guangzhou, who are mainly business people, implementers, they understand the business logic, but does not participate in code development, they are entered into the wrong TFS, through WEB end.
3: Beijing there are some people doing the test, these people are business people, they are by WEB end, to test out the error in the input to the TFS.
4: I am directly involved in development work in Hangzhou home, do the encoding quality inspection, check again almost every day, every line of code inspections.
5: Because we developers are multiple, unified by the project manager assigned to a developer to specify allocation error, so that a clear responsibility, a number of reasonable division of labor.
6: Some quick test, the page of errors, not related to business functions, for rapid results, enter directly into the Word document.
7: The state tracking error management, error correction case of confirmation, etc., need to have some management ability to command.
8: If these errors do not test our own good, direct customers to get there, that one is a shame on the other hand our customers will feel the level of domestic software development is very poor.
A software development team is like a good team, a great need for command and management level, so that the team can play well and most people do not get.
1: the team is not necessarily everyone is a big international players, pay more attention to the overall coordination, full of international players may not be able to win the game.
2: play seems simple, but there is a lot of doorways, in particular, the level of competition the team would like the next level, look simple, really personally play terrible thing is to play football, I do not believe you go to see the kick.
3: The team needs to have a good division of labor, the layout, it is easy to form a lethal team.
4: The team needs to have the captain, the spiritual leaders, coaches, there are some values of unity, we need heart Qi.
5: Many people feel that they play well, but not many people really playing good, a lot of people did not even eligible to play.
After two weeks the whole team worked hard, and to provide customers with high-quality software products, to improve the reputation of our domestic software, not manufacturing principles spam software projects, we have a team of less than 20 people, 10 people less than the development team , which took more than 1,000 errors are corrected well, we all know too comfortable a lot, then you can have more energy to focus on business functionality testing, development, improvement, we do not need to spend time some basic mistakes on, then the tester will go smoother.
In fact, one might ask, there are more than 1000 Bug, is not it too much? Is not there a serious problem? In fact, there is no unified development framework, with no proven components, with no consistent high quality code generator, there is no unified examples of the development program, not just more than 1000 Bug, I dare say you can test out the more than 10,000 a Bug, I have it still effectively prevent the emergence of 9000 lacks far-reaching effects on the basis of the Bug.
It is also possible, anyway, there are more than 1000 Bug, and what they should not altogether hopeless changed, then waiting for compensation contract, waiting for the collapse, waiting to ruin it, you want to forward or back? You can choose your own.
If a piece of software, there are some obvious superficial Bug, then this software is definitely some of the low level.
Why team development and management needs with a good management system Bug? Because many people, it is easy to mess, but more rhythmic, step by step, planned, carry out development work purposes.
Write blog put it plainly, it is to promote themselves, to advertise, to give software developers need to find customers the convenience to find me, so that customers believe I have the ability to manage large-scale software development, has the ability to deliver on time, has a wealth of experience in development and management, Fortunately, the next few years tens of millions of connected software development projects, it is necessary to provide a good future to the brothers, there is a steady stream of cooperative software projects across the country. If it were not for this did not bother to write a blog, in fact, write a blog all have very clear objectives, in order to withstand the blow of others, insults, ridicule, in order to adhere to adhere to write a blog for several years.
Reproduced in: https: //my.oschina.net/iwenr/blog/227675