Dream Break Code Read Note 03

Time passes quickly, the next semester has entered the final review of the examination stage, is a year of graduation, we have also become quasi-senior students, according to the original plan, this semester will be released a total of three dream break code reading notes, this reading notes is the last one, by reading dream broken Code, I learned a lot about software and learned some real-world work scenarios. To their own study is also a great help, but also broaden their horizons.

I spent some time skimming through the "Dream Break Code" a book, deeply realized that one o'clock-all programmers in the definition of a layer is "crazy", "program Ape" is really bad, they are some for the software, the code will be mired in it, but always with the optimist, a bunch of freaks, now, As a computer professional college students, I can only say to myself, you are not they will eventually become them, I know I do not have that ability, not everyone is suitable for software development, I am not that piece of material, because now I have at least touched the fur of C,c++,java and other machine language, Every language is so laborious and sometimes it feels like I've come to the wrong place.
"Dream Break Code" is about Chandler software long and painful development process, in the process, a series of questions to test their program enthusiasts, that moment really feel is not to sympathize with them, in the OSAF Development Group, is solely responsible for selecting other programmers to create software parts of the " System Architect "Anderson is going to face it: what language should be used to write code?" What tools should be used to create the graphical interface of the program? What software technology should be used to store program data? What kind of data exchange standards should be used? Waiting for one more difficult to decide the situation, which makes me feel that the software is so abstract.
Chandler development process in the delay and all the members of the project not to control the creation, the idea of not unified to Maccas many difficulties, in order to the software industry, Maccas paid a considerable price, Chandler designers constantly give conflicting needs, His hard role in such a software industry is helpless, and development is in trouble. Reading this, I seem to know a little bit. All members of the project should be creative as much as possible, but uncontrolled creation will only bring unrealistic project requirements and inability to achieve functionality. The Chandler project is the lack of this "constraint" on creativity, which is the root of all problems. In general, many of the requirements of the Chandler project are contradictory, and the techniques used are somewhat advanced, and most importantly, the lack of a strong management core to adjudicate on the many issues of the project.

After reading the "Dream Break code", 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. Now that you have chosen this profession, you must stick to it. The road long its repair far XI, I will go up and down and quest ...

　　　　　

Dream Break Code Read Note 03