Software culture and subculture
All of these lock phenomenon ring loops, eventually causing some modes. A humanologist Dani Weinberg "Mr. Weinberg's wife. - Translator Note "is my partner, whenever he travels to a new company, we will always pay attention to two important facts when we provide the management method of software organizations. :
1. Any two software companies are not the same.
2. For its essence, no two software companies don't have much difference.
It is precisely because of the first point, it is impossible to have a ready-made method when resolving the true problem in software management. However, at the same time, it is because of the second point. When we comes to a new software organization, we don't have to start from the beginning. Each software organization contains groups consisting of a number of ordinary people - although their quantity may differ, the industries they serve may be different, and the procedures they use may be different. They may be in different countries, and even the age of their lives is not the same. This group will give special attention for this group.
This phenomenon can also be expressed in another anthemode: there is a software culture, which can span time, space, and boundaries of the environment. You have many ways to verify the existence of this software culture. First, English's software book is very popular in the world. To a large extent, this culture is in English culture. The translation version of this book is also very good, so there is a lot of skill in the world. About the software's meeting spans the national boundaries, the survey of participants against these meetings: These people have spanned the boundaries of the industry, and they also break the boundaries of age level. For us, the existence of this software culture cannot be said to be a blessing - because it makes us learn from each other. Therefore, for you or your software organization, our laws you have learned from your own customers will have potential value.
One of the most valuable laws that Dani and what I have learned is: Only a few different modes in the entire software culture circle (that is, all software organizations have a macro type). One way to distinguish these modes is to observe the quality of the software developed by software organizations. We already know that the quality of the software developed by the software organization will also be locked in a fixed level; at the same time, due to the conservative nature of culture, any effort to change the status quo will be contained. From the following characteristics of this cultural circle, you can clearly see this conservative characteristic:
1. The status quo of its current software quality level is self-satisfied.
2. If you want to try to improve its software quality, people first worried that the current quality level may be declining.
3. Lack of other cultures.
4. The software culture is not seen in it.
The importance of quality comes from its value. Therefore, the ability to grasp software quality is the ability to grasp the value of software work. In order to create a new culture of quality software, as a software developer or supervisor, you must know how to effectively respond to these factors - this is also the purpose of this book.
Heliconded prompts and suggestions
1. You may want to be able to determine all the potential users of their own software and understand their value for different users. It is not necessary to say that you can't expect to do our best in these aspects; but this is not equal to saying that your trial is trying to do any benefit. In fact, you will find that even if you just consider this attempt in your own mind, there will be great benefits. Once you don't understand these benefits, maybe you will start to go through the main users to make an interview to determine the value of them.
2. The efforts of any reform will be severely resistant due to the console inherent in culture. You should realize that the purpose of your reform is to better inherit the good way in the past work - after realizing this, you will have to better deal with such resistance. Before starting your reform plan, you should first recognize the value of the original way; even if you want to change the mode of culture, you must first clarify what characteristics you want to inherit - if you can do this, you will get better effect. summary
Quality is relative. The quality of a person, even may even mean insufficient quality.
In order to determine the relativity of the quality, you need to find one or more objects that are implicit through the text surfaces defined.
To this end, we need to make such a problem: What is the corresponding to the end of this narrative about quality?
Unfold, the so-called quality is the value of software products for a certain (or some). It is based on this point of view, and we may coordinate the following arguments:
N high quality is no 纰 纰
N high quality is to provide numerous functions
N high quality is simple and elegant code
N high quality is high performance
N high quality is low development cost
N high quality is high development speed
N high quality is high user friendship
All these arguments may be correct at the same time.
Although we always tried to consider quality problems from deception, it is largely, quality is actually a political or emotional issue.
Quality is not equivalent to there is no error. Even if you can't in line with its needs, a software product may still be determined by some users in high quality.
Improved quality is not an easy thing, because its development organization will tend to lock in some fixed mode. For its existing quality levels, these development organizations have adapted; but how should we do
The amount is raised to a new level, and their heart is not clear - it is like Ye Gong Ye Long, in fact they don't want to try
Implement your own desire into action.
The models used for many software development organizations are not more than a few types (or become sub-cultural groups), which have their own characteristics.
Culture has a backward conservative nature. For software development organizations, this conservative is reflected in the following aspects:
n is complacent about its current software quality level
n If you want to try to improve its software quality, people first worried that the current quality level may be slid
n Lack of other cultures
n will pass the software culture in it.
Exercise
1. I once sent Doug Brent, express my gratitude to him, pointing out two error instances in their software;
But so far, I have not received any reply. If Precision Cribbage has been amended, for me
It is of course not a bad thing; however, I will not pay attention to this correction, because once I can find another suitable
Appropriate procedures to play CRIBBAGE card games, the original software is immediately depreciated. Please discuss:
The value of the software product is the value of the software product when a software product is put into use or the product of its competitors.
Is it a definition of its quality change?
2. In the process of gradually standardizing a given hardware architecture, the software organization will lock in those characteristics? Please list these features one by one.
3. Regarding the quality of the developed software, is your colleagues in your software organization really complacent to the current quality level? What evidence can you see this mentality? If someone dares to spend slightly, how will your business treat them (opinions)?
