I have seen the book called "code Daquan", I haven't remembered, I only remember to talk about a class ratio, that is, "software development" is more familiar with which people are more familiar. Software developed (management, customers, etc.) can get a generally appropriate concept. Many people put "software development" into "building buildings", I also agree with this ratio.
There are a lot of high-rise buildings in Shanghai, passing those construction sites, I often think: even if the software development of 1 million, is it more difficult to build a 10-level building? Although there is also a inferior building, I think that the software system of tofu has much more software system than the tofu. I often ask this why.
I don't know if there is a construction worker who has just taken a second year to host the design and construction of the factory. But I know that
People who have just taken a second year of 1 or even a few months are responsible for the software project.
I don't know if there is an urgent building that can not be idle, and in the case where there is no design drawings, the construction team began to build "Demo". But I often see that the management elites can not be idle, and in the absence of development and design, the driver development team will be "business software DEMO".
I don't know if there will be a customer request for 3 years of building works, compressed to 1 year (the news broadcast is often available). But I often hear the manager of the manuscript asking for 3 months of development time, compressed to 1 month.
Last night, I saw the "Non-programmer" No. 9, and there is a paragraph dialogue in the interview of Alan Cooper (translation):
SmileMac: For example, market pressure, budget, management level, etc. may result in project time limits, and many products are the results of each other.
Alancooper: "... Market pressure, budget ...", all managers cover an excuse to understand the program.
It seems to be extremely emerging, but I think it is a word. Reality This thing is like, no matter how you think it, or ignore it, the reality is still there. It is not easy to face the reality because the reality is always cruel. More cruel more than reality is that management often is very passionate of the land to count the business plan. They believe that "the plan to do to complete is a good plan", as for you to reach where he is not clear. The developers are almost all naturalists, and they don't have "missions Impossible for them." The more difficult the task is, the more vague, the more you can inspire the enthusiasm of difficulties and the so-called creation of freedom. This is a bit like a single Han to see a line of lastria in the dim light, and the clothes are like exposed sexy MM, which is excited to have a physiological response. And when a customer who believes in the computer passionate management person a (group) optimistic, the developer, basically probably a tragedy actor is all, then everyone will imagine the project will naturally fall beautiful Tiancheng Most of the result is "why injured is always me."
I have complained for a long time and I have to mention the software engineering. There is such a situation at present.
Every time the project setback summaries, it will say that "this is because there is no software engineering".
At this time, "Software Engineering" is like a big garbage bag, and any annoying thing can throw it. As for what is software engineering, many people are only afraid only a blurred concept. Most of them can not clear the difference between "software engineering" and "happy life". Many people stand out and say: "Software Engineering is to communicate all the documents in the development, but don't engage in the heart." "What kind of documentation is there?" There are many people who are silent, still There are some brave people standing out to list a list of file names, or come up with "CMM" or "RUP" document template. "How can I fill in these documents and make the information of these documents are sufficient for further development?". "..." a silence. There are several voices in the corner that "find a consulting company to do a plan, or find an industry expert." Maybe someone has such a good luck, but for most projects, this is almost a rat to hang a bell to the cat, and a question is stealing into another problem. Why is a building building, and a software project struggled in the quagmire. I can only say that software development has almost no project compared to the building and other industries. Because in such a short industry, there is not enough failure and lessons to let everyone explore a widely accepted engineering approach. Please note that the summary is a matter, and everyone knows is a matter, but the implementation of everyone is completely different. Go to the kindergarten, we may know what healthy children are like, but we don't know how to give birth to a healthy child. Know the destination, and know how to reach the destination, it is also a completely different things, although there is a relationship. Said here, I suddenly remembered the vow to have a vow, through the CMM X-level, even if they have had children, I am afraid that I have not raised my child because of work.
What is the way out? Only go to the test, try the wrong, and the earth law. What is the price? The cost is pain and failure. The test of software engineering is difficult. A person can try an API for 1 or 2 hours, and 4 or 5 people are not seen in 1 or 2 months, and the advantages and disadvantages of an engineering approach are tried. In the early days of the introduction of a new software engineering, it is also very common in the increase in development and chaos. No one can guarantee that a valid method of someone else is certainly suitable for your project team. Moreover, few bosses are willing to give you a project try. It's hard to returne, there is still a day. Have a senior saying: The experience of pain is the source of improving the process.
Here I recommend two books, and the management will look at each person.
1. "Software Demand" machinery industry, the book is very thin, operability. Do you have to say clear things, why do you want to see a thought?
2. "Software Innovation Road" Electronic Industry. People who write more program should look at it. People who want to imitate objects with MS also should look at it.
Maybe we know how the future is, but I don't know how to live to the future.
The mouse is light, hanging, and smiles.
