Imagine these codes in your mind we can easily imagine the code about ButtIalleradapter. Such as Listing 2-2. When you do
When you can imagine your code is extremely important. We regard the picture as a shortcut to understand the code, not for
Active code. If you draw a picture but can't imagine what code it represents, you are building a castle in the air.
Stop you are doing, think about how to convert it into code as you can. Don't draw for the drawing, you must
I beg you to remember that the code is what you want.
The amount of document: (the principle of efficiency first) For a project team with 12 people work, write a project team of 1 million Java code, I want to be fixed
The document will be 25 to 200 pages, I would rather be less. This includes some high-level structures about important modules
UML diagram document, relational mode ER diagram, one to two sheets describe how to establish system, test instructions, source code
Control command, etc.
I will put these documents in a Wiki, or some collaborative writing, so everyone in the team
Can be accessed or searched from their screen, each person can update them when needed.
It takes some effort to make the document becomes smaller, so this work is meaningful. People will read small documents, not
It is a big top book on the thousands of pages.
