The software development of human-piece set humanization reading notes 02

Comments from the Software development team:

A software development team that wants to achieve maximum success in a project depends on the ability of the team members to form a technical consensus. But why is this so important? Do team members just have to agree on the layout of a table of contents, or create a good bug reporting mechanism? Technical consensus refers not to being able to mingle with colleagues (and of course, this is not to say that there are mistakes in establishing a good relationship between colleagues). Technical consensus refers to drawing on the skills and experience of each member of the team in order to develop better software.

Professional software professionals may be able to quickly understand a good piece of software, at least when they see a good software claim they can understand it, but few of the software developers can understand technical consensus. Many software developers may say that we have used a consensus approach to solve problems, but the effect is very poor, they will cite many examples, for example, some great ideas are buried in the constant discussion, and finally for the so-called integrity of the compromise The project, which could have been completed in 6 months, was finally delayed for 1 years: the ability of the team was not fully developed. But if you listen to their opinions carefully, you will realize that what they say is not a technical agreement at all, but a compromise. (Humanized Software development)

The software development of human-piece set humanization reading notes 02