Reading the seventh chapter eighth chapter of the Avenue to Jane

Source: Internet
Author: User

I read the seventh chapter of "Boulevard to Jane"--the reality of software engineering and chapter eighth--thinking or thinking. In the seventh chapter, we mainly talk about the practical software engineering in some areas needing attention. In the eighth chapter, the author shares some of his own thoughts and thoughts in the process of programming.

Here are some thoughts from the seventh chapter:

The seventh chapter is about the world's outstanding software companies competition, speaking of the real software engineering, in the Software engineering Technology competition is very cruel, the enemy is their friends, the software is not a few software engineers in the dispute between the quarrel, but the result of the large companies in mutual checks and balances, big companies in the fierce competition between the time , ignoring the small companies that led to the emergence of these small firms in fierce competition. It is not necessarily the "software implementation" that big companies take away from the competition for standards, theories, and languages. 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.

The key to the software engineering is to return to the key point of the project, because, in addition to the essential force of software engineering, but also the impact of commercial factors, business also promote the development of software engineering, large companies from the process of self-production from the program has been pushed to its self-acting state. This kind of development may affect the speed of software engineering development, but the focus on the various engineering levels will not change. In the previous model diagram, each longitudinal thin line is used to define a focus, and then the manager who thinks about the project's cost, the manager must make the appropriate inferences about how much the project costs

Ideally, "Software engineering = Process + method + tool". But the real key to engineering success is not how well you organize your team. Even if they are organized in the team, you will face failure as well. If the project is not funded enough, then the project can only be voided, just a dead project, the team will be broken down, not to mention the cooperation to do the project.

The following is the eighth chapter of the sentiment:

The eighth chapter is about thinking or thinking, in the software engineering thinking is particularly important, but only thinking, will be born a new thought, the way to think about the problem can be from the point and face, can also be strenuous efforts. The industry's most commonly used vocabulary is the "top-down" or "bottom-up" distinction. The demand staff will blame the developers for all the blame, and the developers are constantly complaining about the need to be unclear or the endless changes. And if demand and development happen to be the same person or group, then they will start complaining about the client's rigor and the stress of the schedule. Because the goal may be established in the balance, but the quality is controlled in the process. Even with the balance of time, resources and functionality, even if customers, project groups and companies are equally satisfied with this balanced "goal", it may still be "impossible". So the details that we usually say are actually some limited descriptions of the implementation methods. For example, the concept of "software technology" itself, is to elaborate "details of the problem." From this point of view, I am not against the "details determine success or failure" view. But notice a premise: This is the detail of the technique or method.

It is the core content of a project to think before thinking, to think before there is a suitable thought, which is especially important for software engineering.

In short, through these two chapters, I know more about the reality of the implementation of software engineering and need to pay attention to the problems, while in the implementation of the software to learn to work

Reading the seventh chapter eighth chapter of the Avenue to Jane

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.