I. Software Process: Many views have been difficult to accept, but they will then look back to him, and "make sense." Here are some views from the books: 1. Apprentices (that is, people who have just graduated into the company) should start from internal tools (framework?) Maintenance and upgrade. ---- I have seen is the company's technical master to do these frameworks. The first person may not be able to get the source code because of the secret of business. 2. Software technology refuses fine division of labor, software engineering has made detailed division of software development: programming, testing, commissioning, maintenance, which is actually derogatory to developers. ---- Although this is the case, although a person is implemented from demand, the problem is that it is just the opposite of this proposal and mainstream software engineering. Everyone shouted to go forward (there is no way Whether at least, at least yelling), it jumps out "wrong, the direction is wrong," is going to "3. Excessive specialization will delay development, errors. ----- Oh, I have the same top 4. If a 200-person project, 25 most capable and most developed project managers, then remove the remaining 175 programmers, let the project manager programmed development. ----- I don't know that the project manager agrees. 5. The developer's quality will be defeated by the left and right projects. ----- Strong agreement, people are the most important factors in the project. 6. The maintor is a glory identity. ----- My brother listened, I don't know if I will feel better. 7. Best practices are the scientific management of the scientific management, which makes people in order to make a regulations and hinders process innovation. ----- is very surprised. 8. Small teams must never try software projects. ----- I really want to try agile to develop these software development methods, but unfortunately there is no chance, basically, waterfall, incremental development is better. 9. Software development is more intelligent, social work, rather than mechanical work. ----- Now everyone is trying to make it mechanize. 10. The document is always wrong. ------ Agree, it seems lazy to keep the documentation is right, because anyway is wrong, there is a little more and there is no relationship. After reading the reference, some people have written a book, the topic is "How to make a document" 11. Paying to excellent developers higher salary, at least with any administrator (including CEO). ----- I agree, I don't know if the author has persuaded his own boss. This Pete McBreen should be an old programmer, and some stubborn kinds, many points are to see the programmer's perspective, not necessarily right, but many practical experience in the book, see very harvest , Has a clearer and comprehensive understanding of software engineering. A nice book.
II. Reconstruction: Improve the design (Chinese version) of existing code (Chinese version). Lean Software Developments: an Agile Toolkit IV. Patterns of Enterprise Application Architecture 5. UML Distilled: a brief guide to the standard Object Modeling Language (2nd Edition). The Pragmatic Programmer Seven. Does your light are on? - Discover the real version of the problem, Are you your Lights on? How to Figure out what the process real is 8. An Introduction To Systems Thinking Systematic Thinking Introduction (Silver Year Memorial Edition)
