This article is reading "The Pragmatic Programmer - from small work to experts" first chapter "focus on pragmatic philosophy," the notes. Have some development experience after reading this book would be more feeling, the first chapter of the book talked about some of the most basic requirements of programmers, if you are doing career planning, then this book is a good reference significance. Now I combine their own experiences to talk about the contents of the first chapter.
responsibility
Responsibility is to do everything to obtain the premise of your code as small, large life planning, I think this is the cause of it as the first chapter of the first paragraph. Responsibility is something that you take the initiative to assume, of course, if it exceeds your control, you have the right not responsible for it. Otherwise, you need to take the responsibility, even if the process should be honest to admit mistakes, not excuse. I think most programmers will have a strong sense of responsibility for their own code, after all, it's like a child, of course, a sense of responsibility too often lead unwilling to admit mistakes. In fact, in the workplace leaders prefer that employees can take the initiative to admit mistakes, no one can guarantee not to make mistakes, but mistakes conceal it even arbitrary rejection pot of staff, leadership may be more do not trust him to deliver a more important task .
Entropy Software
Entropy is a concept of physics, refers to the total amount of "disorder" in a system, when software sprawl, we call it "software rot." As for what will lead to software rot, the author cites the example of a "broken windows", that is, we often hear of the "broken window theory." In simple terms, a broken window, left unrepaired for a long time, will give rise to a sense of waste. So they broke a window, people began littering, graffiti, final structure of the house was severely damaged, and beyond what the owners of the repair, which abandoned a sense become a reality. Broken Windows Theory inspired police departments are also some minor cases strictly, and preventing the occurrence of large cases.
In software development, poor design, bad code and low-quality documents, are "broken windows", a should see a repair, can not let this state of disorder and more serious, leading to software rot. Of course, we may not have time and energy to clean up all the "broken windows", we can add some TODO, or focus on documenting, pulling a special deal specifically. So, there is no good programmers, only bad design, code and documentation.
Stone soup with boiled frog
Our development process, the need for other team with, it is often easy to ignore the other teams what we do appear to delay. At this time a good practice, we need to put their ideas were landing, design and develop a first edition, there are some positive achievements to share with you. When others see this thing is moving toward success, other people will be willing to help us, and ultimately work together to complete the project, of course, the results should be shared with everyone. To illustrate this problem, the authors tell a story, there are three hungry soldiers, passing through a village, due to years of war, the villagers food is scarce. Then, the soldiers would boil a pot of water, which put a few stones. Soldiers told the surprised villagers said it was "Stone Soup," if you put a little carrot will be more delicious, the villagers ran away to pick up a carrot. The soldier said that would be better put some potatoes, other villagers went back to get potatoes. Then there have been take things, become more and more food, more and more hearty soup, the ultimate soldiers and villagers together to enjoy a meal. This is the case of "stone soup" . Of course, the work will run into some teams just do not fit, just as some villagers are not willing to put their own possession of things out. This is no way, maybe others have more important things to do. At least in this case it gives us a new perspective to solve such problems.
From the perspective of the villagers, this case also warned us not to be too narrow field of vision, to pay attention to what other people do, if it is a worthwhile thing we should actively participate in, pay attention to the big picture. Do not stubbornly only responsible for the content of their own that one, do not do the frog in warm water. So, stone soup and boiled frog seemingly two separate cases, there is some connection.
User involvement
Perfect software requires user involvement, because usually we are writing software for others. In addition to the functional requirements of the software, but also concerned about delivery time, software quality requirements, ignoring the needs of users, the blind pursuit of new features, there are not whitewash the code of practice professionalism. In my engaged in big data work, which in fact is our customers operations, products, if they ignore the data needs, blindly add some cool indicators, the analysis of the product and may not help, obviously this is wrong of. Also, for the delivery period, while ignoring the quality of the project functional requirements of practice nor desirable. So, we often need to meet the perfect trade-off between user needs and engineering practice.
Knowledge assets
We often hear that the programmer a young person, that knowledge assets are time-sensitive. With the lower value of our knowledge, our company or customers, our values are lower. In order to prevent such things happen, we need to treat financial assets as treat our knowledge assets. Learn a new programming language each year, read a book each quarter (regularly invest their own). Learn more contact with other technology stack, such as: do understand the front end of the back-end technology, bigger and understand the algorithm data (diversified investment). Focus on new technologies, new technology before the epidemic will take the time to study, when it is popular we are leading the majority of people (buy low and sell high). Always assess their grasp of technology in the market place, if you have a cold, determined to give the required experience into a new direction (periodically re-evaluate the assets). We often take foreigners to refute programmer young rice to eat, read this section only to find that foreigners knowledge assets as financial assets, so as to ensure their value.
communicate with
Although programmers life is not very talkative, but at work often requires a lot of communication, small interface protocol, large architectural design. On the one hand it is to promote the exchange of their work, on the other hand to the output of their point of view, to establish their own influence. At the same time the exchange process requires attention to some details, such as: Know your audience, choose the time of communication, choice of communication style, pay attention to his ideas before the communication, whether the document is clear, the exchange should listen to the opinions of others, let the audience participate, sum up the communication , reply others.
summary
In this part summary of each seemingly more independent, but in fact there is a certain link. First responsibility is a prerequisite for the subsequent so content. Secondly, as a programmer we want to do their own work, "Entropy Software" tells us to be based on our own work, to solve their own software in the "broken windows." When we do their own thing, we need other people to participate in the software, consisting of a large collaborative body when we need to how to collaborate, it is the content of a "stone soup with boiled frog." We develop software, and ultimately to solve the needs of users, create value for customers, so the process must be "user involvement." Although we have developed a customer satisfaction of products, but knowledge of the process we use time-sensitive, "knowledge assets" This section tells us that if let yourself valuable. "Communication" last-mentioned is to make all the efforts possible to output, to establish their influence above us.
Welcome to public concern number "crossing the yard," I will be sharing more good books
