Read the Seventh Avenue to Jane. The thoughts of eight chapters

Read the Seventh Avenue to Jane. The thoughts of eight chapters

With excitement, feeling the mood to read the road to Jane, after reading, the heart of feeling, to our programmer's understanding and experience has a deeper experience and feelings. Also have a preliminary understanding and plan for their future development direction. In my mind, also deeply injected a programmer should have what qualities and abilities. The experience and some important ideas that are mentioned in the Boulevard to Jane are very valuable assets to us.

From the earliest focus on software development tools to the present, the software industry's giants have been in the endless ideas of nirvana in the back and back. There are so few people, in the forefront of creating information, their ideas, thinking, practice and re-thinking and practice, are the software engineering in the development of the road to leave a solid imprint. The authors write that the big companies ' contention for standards, theory, and language is not entirely due to "software implementations". To unify the theory, the Unification tool, the unification process the attempt, its ultimate goal is in the entire software engineering system the overall victory. The vast majority of people on the abacus are just an operator to calculate the outcome.

So here, the most important thing is engineering, a company, an enterprise value is also engineering. From program = algorithm + structure to method, to process, engineering, finally to management plan plus details of processing and implementation. The mission is to achieve the purpose and realize the interests of the company.

For the idea of AOP, what we need is to master a certain method, program, use tools and according to their own ideas to program, to do a project.

The author keeps referring to tools, methods, and processes, because these three are called three elements of our software. Every element contains many aspects, from each isolated level, but in essence, we should return to the ontology of software engineering to think about the problem, rather than just focus on every element of the local. Because, the overall problem of the project is still "realization".

For tools, our goal is to communicate, not to "choose Tools", so the language of communication should be chosen to ensure that its symbolism is sufficiently accurate and detailed in a diagram, and that it can provide sufficient information for different readers. Therefore, the use of UML diagrams in the project, there should be a corresponding text to describe it. And the correspondence between this description and the graph should be maintained continuously. If this relationship is loose and fractured, then the next person to read the UML diagram will face the same dilemma as when the Oracle was unearthed.

The operator is far from the developer and vice versa. Boss is the title of the operator, not the title of the developer, an operator does not need to know the technology, he only need to put this company, the enterprise to run well, to achieve the maximum output effect. So the operator and the project manager to do is to coordinate the communication between the operator and the developer.

When we encounter difficulties, we have to do is to solve the problem as soon as possible, from the time, resources and functions to discuss the objectives of the three aspects. For some minor problems, the administrator should try to avoid it. The most stupid way to do this is to forget whether it is a detail or a stub, so as soon as you feel your toes are stuck in the mud, look back. To feel with your toes is sometimes more effective than thinking with your mind.

For us, the most important thing is to achieve the goal, to achieve what we want!

Read the Seventh Avenue to Jane. The thoughts of eight chapters