"Dream Break Code" Reading notes of the second

The following is the chapter directory of the Dream Break code:

I'm going to read it detailed slightly 3 times, this is the first time, 0-3 chapters;

after reading the 0th chapter "software Time" I have an idea "this dude is talking about God horse, seemingly no logic to say." But think about it. He is giving us a brief history of the general development of software and we will be in the future (oh no no no) is bound to encounter the old and old many bugs let us headache, Software Engineering Although the project but he and ordinary bridge paving the road is not the same, it is more abstract logical stacking with the author of the word is "trouble a bunch of" think about it, I have done a good job of my own and even take a sleeping bag to sleep in the office preparation. But the software engineering this profession even this profession cultivated talented person still is very worthy of respect because now the life already can not be separated from the soft ware it penetrates in the various trades small to a toy to reach the aircraft carrier.

After reading the 0th chapter has the idea: my software engineer Road is very long, there are many doomed bugs waiting for me to challenge, to defeat; Software engineers are a very sacred profession, because the world becomes more intelligent and civilized because of our existence, as the author puts it:

So I'm ready to go to hell:

See the first chapter when the name of "dead" is very strange ah, originally only a cited example, this chapter from a few programmers do not finish the work on time to summarize the reasons for the beginning of the meeting, triggering a lot of examples, I would like to talk about the individual to the author of the example of understanding, Well I'm a ears inexperienced program ape (labeled).

NO1. Writing programs is often not as scheduled as programmers expect, because there are always hundreds of of thousands of bugs waiting for you on the road, and you expect four hours of work to be done for six years or not (as the author says),

NO2. In the previous time all the source code is not open, because the company will see the source as the core of the profit is the company's treasure, know that there is a genius of the great God appeared, his name is God Demon? ——

Thomans (who personally felt that Thomas had listened better) broke the deadlock and made software programming more flexible and more efficient.

NO3. That's one of the classics in this chapter, a rule that says something like this: a delayed project or project, the more people you add to the project, the worse the delay. what?! Is this not a paradox, but after a lot of practice he is right, as a quasi-programmer who has not yet taken part in the job is really teachable. The reason is actually quite simple, a project from the beginning to the completion of planning, and in the process of doing the project everyone responsible for the module is different, a new person to add to this project, first to understand the work of predecessors and code, but also to find out what they want to do God demon, But programming this thing torture abstract and code tens of thousands of lines, it is not easy to move, so add new people will delay the duration.

The 23rd chapter is written together;

When I see the second chapter of the topic "Agenda Soul" When I was confused, agenda is what? (Forgive my ignorant) later a look, the original is a Lotus company developed a smart software, and widely praised by users to occupy the majority of software market. The second chapter mainly refers to the development of several large software companies and the case of the truth, reading is more interesting. Since the title is called "Agenda" soul, will inevitably analyze Agenda this software for the magic will be widely praised, the article said:

This is to say its features and features.

Here is the idea of the designer:

Yes, from the user's point of view, the design of the user feel the most comfortable use of the tool you can sell the work. I think this should be the core of the second one.

As for the third chapter, I am more deeply aware of the difficulty of making software, it is like an onion layered, each layer is painstakingly built on the foundation of the previous layer, at stake.       Anyway, over the years, a layer of building up, that is, "abstract cascade", and the lowest end of the abstraction layer is the assembly language, is the most let me learn the headache of assembly language, is also most difficult to learn and write, and later produced a lot of more applicability of the high-level language, and then there is a compilation. Python was later invented, and although the scripting language was not as much appreciated as other high-level languages, Python, by virtue of its own merits, played more intelligent features than other prophecies, such as its lenient principle on variable types. It provides several other unique mechanisms, more in line with industry-standard programming languages, and also "object-oriented." But it is not perfect, of course, the world can be called the most perfect thing is always with people's demand and expectations, there is no.

"Dream Break Code" Reading notes of the second