Job Three: Code specification, code review, PSP

1. Whether code specification is required (5 points)

for the need for code specification, consider the following arguments and refute / Support:

1. These norms are the result of bureaucratic waste of programming time, affecting people's development efficiency , something that wastes time.
2. I am an artist, a craftsman, I have my own norms and principles.
3. Norms can not be forced to all, should allow many exceptions.
4. I'm good at coding, you can listen to me.

See:

http://www.vaikan.com/the-conventions-we-follow/    

http://www.aqee.net/things-everyone-should-do-code-review/

http://scientopia.org/blogs/goodmath/2011/07/14/stuff-everyone-should-do-part-2-coding-standards/  

2. Code review (ten points)

Each student reviewed his/her partner's personal project (the arithmetic programming job in the second assignment) and recorded the results of the review in the blog.

The Code review checklist can refer to

[1] the contents of the4.4.5 section of the textbook "Construction Law"

[2] http://blog.fogcreek.com/increase-defect-detection-with-our-code-review-checklist-example/ .

3. PSP Records personal project time-consuming situation (5 points)

Please refer to the textbook "Construction of the Law" 2.3 Table 2-4 PSP2.1 report on the completion of arithmetic programming time distribution, published to the blog.

This job deadline:

Submitted before 8 o'clock in the morning March 24 . Late delivery of 0 points (based on the time of the blog), late 2 weeks and 2 weeks or more, turn off the operation points.  

Job Three: Code specification, code review, PSP