Dream Break Code Read Note 02

Imperceptible already to the eighth week, time flies, half semester passed, our software engineering also to the first sprint stage, recently we devote ourselves to our team project, of course, in the work also did not forget to continue to carry out my dream break code reading activities, this week, I read the No. 4567 chapter of the content, also have a lot of knowledge to summarize, have a lot of sentiment to record.

First, read the content

The title of the fourth chapter is Le Gao Wang, described in a large number of programmers unemployed or semi-unemployed technical industrial Ice Age, Osaf benefited, many people into the Chandler project, understand the software developers often talk about the front and back-end concept, the foreground is the program and the user to deal with the part- Show form dialogs and mouse instructions to tell you what's going on, giving you a way to enter information and get output information. Background is the foreground event and the user input direction of the place, the computer to the event and input processing, save, retrieve. The front desk should be sophisticated, intuitive, powerful, and the backstage should be invisible, efficient, rock-solid. However, Chandler backstage work is in trouble. The primary requirement for the database is to facilitate front-end developers, and front-end developers need a mechanism for "object persistence". The simplest way to achieve "object persistence" is to use an object database, which stores a piece of code and the data associated with it. The next step was to refine the Chandler project, which led to the Zodb, which raised the word Lego: New Zealand scholar James Nobol and Robert Bi sometimes wrote with the pseudonym of "postmodern programmers", who called the Dream "The Lego Hypothesis". After all the programmer's efforts Chandler completed the first edition.

The title of the

    fifth chapter is the bundle of geek and dog, which begins with a dog named Chandler, and then reflects the similarity between the dog and the program, and sees Osaf on the dog with a flea powder on it, and then stickers the label saying: "Killing fleas-don't touch me." Some people like to label themselves, such as saying: I do not program, I do not, I am a fool of people. This label is self-attached to oneself, and then there is reason to shirk responsibility, do not do their own things. In fact, this is a manifestation of self-deception. Moreover, we should not give ourselves this quick conclusion, because you do not know how much potential, perhaps we just lack a kind of confidence, lack of a kind of courage, like the teacher in class to see a picture, a rooster walking in front of a group of dogs, to the dog review, this is a kind of courage, we Shong is this with courage. So we should be like runningmen, dare to tear off the label. One of the words learned: Geek out, geek, refers to immersed into the details until the abnormal state-and bored. According to him, the geek is not all programmers, but programmers are all geek. There is no reason for me to comment on this, but our army programmer should be a geek. Because we have to write the program must go to the end, if not meticulous to complete the work, to the later to fix the bug is often several times or even dozens of times times before. And we do things must be able to use, so that the amount of customer satisfaction can be, the times in development, if you do not have the perfect design, you will be eliminated, this is the reality. So we're supposed to be geek.

The title of the sixth chapter is to fix the design, and he argues that software design does not just seem to cover a layer of tempting graphics on the programmer's behalf. It is a creative foundation for imagining user needs and meeting these needs in a software architecture. Yes, we have to take advantage of the people users really do not follow the instructions you write to work, their operation is sometimes difficult to fathom, like a chapter people do not follow the rules to write text, and finally the programmer himself at the end of writing a button: automatically edit the text. Like, the author suddenly accidentally dragged the file to disappear, it really makes a person, but the undo key saved him. Both the edit button and the Undo key are intended to enable the user to use the software or the operating system well. We do software should be like this, to meet the needs of users, like now teachers just let us do a software, which will have one is: to facilitate users. It says: Don't expect to achieve success in a short period of time, start with a small project, and never expect him to get bigger, if it's so small, he'll do over-design, make him think too important, and worse, be intimidated by his own imaginary hard work. So to start from a small place, focus on the details. Don't go to big picture and good design. If the project does not address some of the immediate needs, it is mostly over-engineered. These really taught me a good way. We have to do a birthday reminder software, we have a lot of ideas that we like, now think of our ideas a bit more, and want birthday reminders and want to be interspersed with a lot of design, so many things to really do when you will find it difficult, and then the final result we may be giving up. So let's start with the small.

The title of the seventh chapter is the detail view, which focuses on the effort of the programmer to do the detail view, but the consequences of the demand are mistaken, like the guitarist Jill. Taft's design Sketch: An extra apostrophe makes a 18-foot boulder into a 18-inch stone column. Learn about the most famous and notorious variable naming scheme is the Hungarian notation. The name comes from the native name of Charles Simone, the inventor of the language, and also from the mysterious and hard-to-pronounce word markers in the languages, which may be needed in the era of writing Windows programs in C + + because of the bewildering variety of types, structures, enumerations, controls, and so on, and in Java and C # This type of nomenclature is a complete violation of the programmer's aesthetic in such strongly typed languages.

Second, personal sentiment

Previously, I do not understand the development of software engineering has so many twists and turns and difficulties, for us now every program development software is not very clear, by reading the contents of these chapters, we know that the software we use now hard-won, and its design of the author's hard intentions. Let me have a feeling of admiration for those ancestors who were not.

Now, I really think that the software development process is abstract and arduous, not everyone can do a job, machine language is not more difficult than human language, the development of software is like building engineering, a layer based on a layer, the need for patience and a dedication, a group of people embrace the dream of changing the world on the road, but in the pursuit of the discovery, Those close to the ideal peak, become so far away, every time a mountain in front of the mountains, always thought has come to the foot of the ideal peak, but found that this is another need to climb to overcome the barrier peak, I think in fact, although we are now standing on the basis of previous development projects relatively easy, But we still lack the spirit of daring to explore, and that spirit is not to be lacked in any age.

By reading the contents of these chapters, I think to solve our current problems, we should learn the spirit of the book programmers to explore, although Le Gao Wang is only a dream, we should be brave to pursue the dream, to put into action, so that in the face of difficulties, not without a response, so I think in the future, We want to be like the programmer in the book that is not afraid of difficulties, dare to explore!

Dream Break Code Read Note 02