Dream Break code read one of the notes

No. 0 Chapter software time

See the No. 0 chapter, it seems that does not conform to the routine, but also the programmer can have the tacit.

The 1th chapter is dead.

The issue of software delays is common. The Brooks rule implies that the ideal development team model is a single developer who doesn't have to stop working and communicate with colleagues.

The 2nd Chapter Agenda Soul

Each project has a different place.

3rd Chapter prototype and Paython

Software-making people like to talk about bricks, while skepticism is a serious sight in the castle. In any case, over and over, build up one layer at a A.

"Abstract Cascade", whenever a new layer is added, it is necessary to transform some complex and special things into simple and universal things.

As you move up from the bottom of the stack, farther away from the machine, you are asking the computer to do more work.

Fourth Chapter Le Gao Wang

The simplest way to achieve "object persistence" is to use another database technology, the object database.

The programmer's "thinking model"--on how the program does not pick up how to assemble, where the data is stored, and what happens when the user finds or moves the data--is aligned with the user's thinking model.

Dream Break code read one of the notes