The day before yesterday reading about the record share it. The company recently began reading regularly held to share training, the overall feeling is quite good. This time it was my turn to share, will be ready to share in agile software development book.
However, sharing out the effect is not very good. I feel we did not seem very interested. I think I have to explain is not OK pot. Not enough time to exercise more than a few times.
The day sharing the content simple record.
What is Agile?
I think agile is an idea, development model. Different from the waterfall, he plans to hate hate step by step; he advocated to embrace change. The reason for his appearance is true, because now, more and more changes in demand occur. The only change is not a change in the world.
Identify changes in the same part of the software when numerous, and the constant part of the abstract, is a method to solve constantly reworked.
Changing needs, communication is always of poor quality. And user needs, requirements and design, design and development ...... or even turn a few more hands. Everyone just an intermediate layer, the initial idea conveyed through a few hands, the hands of time to develop have no idea what kind of misinterpreted. And that means rework. Made out of things sent to the scene, is not satisfied with the various ...... Then later, I learned packaging, the code is written from scratch, all of a sudden do not tail. Where there are duplicate code, in order to firmly method, the inside of the variable to extract. Otherwise, that is, the slightest movement, it is necessary to change the rhythm of a lot of places.
Individuals and interactions over processes and tools Working software over comprehensive documentation ...... yes ah, the software has always been user will be able to get a hand with the best. The success of the world face software, which requires people to look at a software user manual in order to operate? However, we do projects tend to require each user manual.
About the middle layer, I think this book is the most a sentiment point. See "Software engineering difficulties, no one is adding an intermediate layer can not be resolved."
We are of the intermediate layer, with the intermediate layer are also things ...... binary mask circuit complexity, the complexity of the operating system mask of 0 and 1, java masking operation system complexity, these we developed, a computer language and shield the complexity of natural language, designed to shield the user documents and the complexity ...... everyone is a middle layer, called method other people, other people also call the method.
Recommended reason:
I recommend this book point for all those who see the Internet industry practitioners. Easy to understand, a lot of analogy, combining theory with practice. It also allows us a new idea to look at the problem. The book contents: UML class diagrams, agile software development ideas, practical cases, design patterns, object-oriented principles, as well as Appendix 2 on agile funny articles and paper. A reading value.
Ok. . Also do the best I can do to prepare, and the next have the opportunity to properly prepare it!