Dream Break Code Read Note 01

Continuation of the previous book, "The Law of construction" good reading habits, I began the "Dream Break Code" reading. There are 12 chapters in this book, and the next one will be divided into three reading notes to complete the reading of the book, and the first four chapters will be read in this reading note.

First, read the content

With a very curious mood, I began the 0th chapter of the reading, the title of this chapter is software time, in fact, roughly browse the directory found the title of the book is actually very flexible, and some titles let people feel puzzled, but I believe that when I read this book I will be enlightened. In this chapter is mainly the editor's readme, read more want to read a novel, in the editor's Readme can be seen in his programming experience, from his body is actually can see his shadow, because in the future I will also be a programmer, that state of mind is I can feel and experience, One of the words I think makes sense, the author of this chapter titled 0th Chapter, is to point out a small difference between computer programmers and others: programmers count from zero, not from the beginning. The author of this small funny actually also makes us resonate. In the author's narrative I also learned that the development of software and the process of a lot of great researchers for its development and contribution, let me deeply realize that the software engineering skyscraper is not able to cover all of a sudden, it is necessary for us to pay millions of times times the effort, this chapter makes me the development of software engineering into deep thinking ...

    Next begins the second chapter of the reading, similarly, the title of the elusive--dead, with the mood of doubt I continue to read, this chapter is also the use of narrative way, the beginning of the programmer because it is not finished task and plunged into deep distress, One of them thought that the reason was that there was no blueprint, and that there were unpredictable problems, while another thought that there were too many uncertainties and that the time required depended on the time spent by others. However, the 44th defect they recorded in the Bugzilla had not been able to repair for a long time, but at first they thought it was a small problem, and they did not expect to spend their time, and the final opinion was unanimous: black hole-type flaw, that is, cannot determine the length of time required to fix the defect, The bugzilla should be marked with special warning words, and later mentioned that software projects are difficult to achieve on schedule, which is very common and tolerant. In the world of software development, progress has been so widespread that people deliberately sporogenous out a euphemism to describe it: slippage, which means stalling. The author uses a very figurative metaphor to explain the situation: as if a cable was hidden in a software development project, the cable was tight, the progress was rapid, and the cable was disconnected, the work stopped. Historically, however, any software has had its hidden cables, and efforts to improve software development have been made to keep the cables tightly fastened. Friedrich Wilderness Brooks, in the Myth of Man and month, once said that the earliest and best diagnosis of the problems caused by software time. He has also mentioned that software developers are usually optimists, who think that every flaw can be quickly corrected, and that correcting old flaws will reduce the number of new defects, and that the blind optimism, coupled with the programmer's desire to please customers, tends to derail the process from the start. Every effort to anticipate and schedule project progress is a dangerous and deceptive myth, the so-called man-month, a scientific management concept that assumes that productivity can be split into discontinuous, non-differential, replaceable units. And Brooke observes that people and months are interchangeable only when tasks can be assigned to many workers who do not communicate with each other. Knowing the Brooks rule implies that the ideal development Group is a single developer who doesn't need to stop working and communicate with colleagues. The Academic computing field has been advocating Kaiyuan, 1985, MIT geek Stallman for the commercial software industry closed code habits hatred, founded the Free Software Foundation, issued a special license, will be all code, reuse combination into the new product, This license, known as the GPL, is clearly intended to limit the privatization of free programs, but critics have seen him as a terrible infectious disease virus. Until then, the open source software development model was summed up. Kaiyuan not only provides an alternative economic basis for the production and distribution of software, it also can completely change the specific process of software development. The cathedral model was learned in Raymond's "Cathedral and Bazaar". Next, I learned that LotusThe founder of the Flower Development Company, Osaf, learned about his hard work creating a software company and the travails of the developers and the Chander of the project.

    Soon read the second chapter, the title of this chapter is the soul of agenda, this chapter of the plot continues the first chapter of the content, the beginning of the theme is still the Chandler project, it is to change the world's dream driven. Then referred to exchange, which led to the peer-to technology, the name of the Lotus Company, and released the agenda this project, this is a simple list management software, but there are several prominent features to make it into the software legend: Management of daily life, organization of academic research, music collection, work projects. It also introduces a new means of managing data-between the strict structure of traditional computer databases and the free form of word-processing software. Agenda broke through the strict logic of the computer and the human vague between the barrier, in this piece of loess to expand a new world. In today's society, programs or websites always ask you to fill in the blanks in the way it is set up, not your own--the social security number must not include a hyphen, the credit card number must not include spaces, and Agenda has a unique secret to allow users to enter at random. However, it has failed to reach the realm of killer applications. Part of the reason is that Lotus, which has become a behemoth-class company, is eager to triumph in the commercial market. Later agenda was abandoned by the company. In his efforts to create an open network, the agenda project, he cherished the dynamic adaptability of the program, he decided that no matter the appearance of the new software, must have the spirit of agenda. It then introduces the link and the appearance of the mouse and the meaning of the boot belt: improve the process. Engbart that the boot belt is more of an abstraction, a mystery, and not just an engineering problem, in terms of achieving the goal of smarter enhancement procedures. We also learned about the third-order phenomenon, which does not improve the process, it improves the rate of process improvement. In 05, the FBI launched the Trilogy computer modernization project to build a more secure and modern digital communications network, but in the face of the dilemma, this chapter let me see the emergence of a software and the misfortune, as well as the twists and turns of development.

Soon came the third chapter, the title of this chapter is the prototype and Python, the beginning of the example of the CD with the introduction of the early stage of each programming project, when the team chooses language and technology, ready to cut and development, will be limited by their own tools and materials. In his experience of absorbing agenda, he has studied how to describe anything in a three-segment pattern, which looks like the structure of the subject-verb-object in English simple sentences, but the semantic web has outlined its contours, based on a technique called RDF (Resource Framing framework), which uses triples to store all the information. Later I learned about Vista: a user-oriented program that focuses on presenting data to users, focusing on how to enter, organize, and modify data. Then learned the development of the OSAF, the rise of the chip, the birth of the assembly language, the birth of many programming languages such as: Lisp,cobol,algol,basic and so on, and then learned the first widely used is the FORTRAN, It summarizes the laborious process of writing assembly language as a short command, and has achieved success. One of the reasons for its success was that it challenged experts ' predictions that such high-level languages would run slower than hand-written machine code. In the era of Fortran, computer time is quite expensive: machines are scarce, bulky and expensive. The Babel of many programming languages have been erected, and these languages are both rugged and fragile. Later, Hertz used the Python language to write the Vista prototype. Python is an interpreted language, and the compiled language is then run by the compiler by translating the programmer's source code into machine-readable binaries, while the interpreted language does the same thing at runtime-the interpreter translates the source code one line at a time and then runs the processor. We then learned about the Python language, and the intense competition with Perl, but eventually using Python,python open source and cross-platform, the same Python program can run on Windows,macintosh and Linux systems.

Second, personal feelings

Before, I did not feel that a software project will encounter these troubles, the road will be so tortuous, after reading the contents of these chapters, through the said, those researchers for the development of software engineering to make me very admire, perhaps the software and code we contacted before is too simple, and not aware of these problems, There is no such meticulous thinking, there is no such detailed in the Timeline of the history of the software and the middle interspersed people or things, to agenda and Python these words are also very unfamiliar, do not know how they were proposed and improved and developed.

Now, Lenovo to us, I think we do the project when there is no innovation, no improvement is because we are not in the face of the problem is the effort to think, the book said the researchers in the face of problems are hard to study, after overcoming a difficulty after success. Another way to solve the problem is not found.

By reading the contents of these chapters, I think to solve our present problems, we should learn the spirit of the book researcher, through the whole narrative process, let me seem to see that era, each researcher's efforts, pain and melancholy, The problems they encountered and the circumstances in which they were present and the products created in the particular environment made me new to the development of the software, from the middle school to the solution of the software black hole and the difficulties encountered, and the great researcher's style, which is very worthwhile for us to learn. Now, I know that in fact, we still have a lot of things not to do, so in the future to do the project to continue the cautious research attitude of the predecessor, encountered problems to seriously do a good attitude.

Dream Break Code Read Note 01