Simple Beauty-thinking of software development practitioners 01

A few days to read the Kian Daniel wrote this piece of the flavor of the work, mainly on the software development process of some thinking, book. The author's way of writing is very special, through the narrative of the story of the software development of a complete set of processes and procedures need to pay attention to the place. The author's main attitude is critical, with idealistic colors, yet it is thought-provoking.

This book gives me the biggest gain is in software development to learn to think. Consider the purpose and meaning of all the steps and methods that exist. Compliance with the development trend of the software development industry.
The author mainly deals with the methodological level, overlooking the development organization and people on the land. The problems and solutions that are seen are often directed to the essence.

Here are a few impressive insights and nouns to remember.

The quickest way to learn new knowledge is to incorporate new knowledge into a set of knowledge systems that you understand. Therefore, it is very important to establish the connection and difference of each technology while learning, which is helpful to build up your own system. Cultivate good internal strength, in contact with new knowledge, can quickly get started and understand its essence.

The essence of software is 2 binary and with non-logic. The essence of software development is human creation, and the root of creation is the imagination, which leads to "metaphor" and "story". Metaphor refers to the events and relationships that are abstracted from the life experience and the running flow of the software to be developed. The story is the way the story is told to imagine the process of running the software. On the 6th chapter on software Testing
This chapter discusses the nature and principles of software testing. Software testing is a kind of destruction that makes sense only if the destruction drives the building.
We use a one-time test (and subsequent performance tuning) as an example to illustrate the significance of the damage. In this performance test (performance tuning) process, almost all of the problems can be solved in the software production process, which shows that the software production is not complete, but does not indicate that the performance test is successful. In other words, if we still encounter the same problem during the next performance test, the performance test has little meaning in terms of software development itself (non-commercial factor).
In addition, there is no design, it does not matter test. Software development is inseparable from the team, but, what is the team, how to play the role of the team, many people are not very clear. Therefore, we often see team building and team management go into all kinds of misunderstanding. For example, team decisions, non-accountability management, and so on. This chapter is a reflection of these issues, a detailed discussion of the values of the team and the communication of the team members.

Simple Beauty-thinking of software development practitioners 01