The law of construction reads questionable
In nearly five classes of time will Xin Zou Teacher's book "Construction of the law-modern software Engineering" the second edition of the general reading. Although the book is a relaxed tone with some interesting conversations with "company staff" to transfer ideas and ideas, it is not easy to read and understand, and in the process I have doubts about some of the ideas in the books, now the problem is listed below.
- P68 page: I do not quite agree with Zou Teacher's "mastery" of the cube's determination method. As if in software engineering development, a person solves a bug. Solve the bug is not "proficient", but also to recover the bug, reproduce the bug is to understand the principle of each? I think as a software developer, we have the skill and ability to solve the bug, do not need to master the means to reproduce the bug.
- P79 page: About the use of Goto. To be honest, this is the first good word I've seen Goto. I have only seen Goto in the operating system under the source of the use of the situation, of course, at the bottom of the operating system use goto skip to error handling to avoid unnecessary duplication. But using Goto even at the bottom of the operating system should be used with caution, do not know what the teacher Zou think there is a situation that is "conducive to the clear embodiment of procedural logic?" ”。
- P89: Here I have a puzzle about pairing programming: If the pairing partner does not communicate with me and is not passionate about pairing programming, this pair programming will only make it inefficient. In this case, in addition to the exchange of partners (generally outside, involuntarily), how can improve the effect of pairing programming?
- P85 page: Is it really necessary to unit-test the code path that cannot be run to? Especially in the case of good encapsulation, forced to disassemble the function for unit testing, the class added a lot of useless methods? How does the teacher think about this problem?
- P117 page: About Agile development. The agile development model can be said to be a lightweight model, but there is a serious problem in front of us: the small entrepreneurial team once agile developed a creative and excellent software and to improve it to a good degree before the release. Will this attract the creative plagiarism of big companies? How to solve the problems that may be encountered in agile development, especially in the case of financial resources and people who are inferior to large companies?
- There is also a personal question to ask the teacher: why the first-time software engineers in the industry are always self-confidence in their code style and efficiency, and always want to refactor the code of others? What is the degree to which a project is to be called non-maintainable, and in what circumstances is it justified to be reconstructed?
The advent of software and software engineering
The term "Software" in: 1958 Turkey in the paper "The Teaching of Concrete mathematics" presented.
The original wiki is:
In +, Fred Shapiro, a librarian at the Yale Law School, published a letter revealing thatTukey ' s 1958 paper "The Teaching of Concrete mathematics"ContainedThe earliest known usage of the term "software"Found in a search of JSTOR ' s electronic archives, predating the OED ' s citation by the years.
The term software engineering was coined by Margaret Hamilton when NASA designed the software on the Apollo computer.
The law of construction reads questionable and personal WEEK1 work
