By: Ron Jeffries; Ann Anderson; Chet Hendrickson
Publisher: Addison-Wesley Professional
Pub. Date: October 16, 2000
Chapter 10 : Quick Design Session
XP declares that after a story is broken down into tasks and there's still questions held by the programmers, the team should sketch out a design, discuss code structure and objects, and listen to ideas. This process should only take 30 minutes at the most.
Chapter 11 : Programming
The actual programming portion of the XP coding mantra advocates:
1) testing often - Testing often reduces bugs since bugs don't build up in number before they're fixed, there's fewer dependencies, and programmers are more familiar with the code at test time.
2) pair programming - Next Chapter
3) collective code ownership - allows programmers to improve all code when encountered which increases readability and reliability
4) simple design - code with a simple design is easy to modify, is readable, and tends to be efficient. A simple design consists of four properties that lend to quality code:
a) Runs all the tests
b) Expresses every idea you need to express
c) Contains no duplicate code
d) Has the minimum number of classes and methods
5) refactoring - refactoring is the tool used to keep the code within the simple design ideal and reduces bugs.
6) continuous integration - Since integration causes bugs to appear through the interaction of multiple components and bugs are best found early, integration is done continuously; or in other words, several times a day. In line with continuous integration is the idea of keeping build times low enough so that continuous integration can be done.
7) developing a coding standard and conventions - Since code is collectively owned and refactoring should be done on all code, it's important that the code is understandable and readable for the entire team. As such, common coding conventions and coding style should be enforced. Some issues for standardization include:
a) Indentation
b) Capitalization
c) Commenting
d) Method Size
e) Names
8) limiting overtime work - Rushing to meet deadlines produces bad buggy code. Therefore, it overtime work should be limited and scheduling done accurately.
Chapter 12 : Pair Programming
Pair programming is where two programmers code together and where one acts as a "driver" and the other programmer acts as the "partner."
The driver does the programming while explaining what he's doing and what he's thinking making sure that the partner is engaged.
Meanwhile the partner is actively engaged watching for syntax errors, making sure the driver adheres to the team's coding style, and keeping an eye out for mistakes, pitfalls, or confusing code that the driver might make.
Pair programming allows the driver to focus on the code and lower level issues while the partner can focus on higher level issues. This separation of concerns allows for complementing ideas to enter in simultaneously and results in clearer quality code.
The Design of Future Things
Design of Future Things
By: Donald Norman
Publisher: New York Basic Book
Pub. Date: November 2007
Chapter 4 : Servants of our Machines
Norman begins this chapter by relating a fabricated story where a Mr. Newone got stuck in a traffic loop in his car. With this story, he makes the point that with automation comes unforeseen errors and complications in even well engineered intelligences. From there, Norman explores the relationship between technology and human activity from a historical perspective. Norman claims that there's been a fundamental shift in the understanding of technology and the way in which technology interacts with the user of the technological tool; primarily, he claims that automation technology is not fully automated and requires human vigilance and insertion of control in dangerous or unexpected contingencies in the control loop.
This mode of interaction does not compliment human strengths of tendencies and Norman argues that technology should be either fully automated or not at all.
Norman also claims that automation is reducing human understanding and awareness, but more importantly that new technologies introduce unexpected outcomes, both good and bad. Finally, Norman discusses the platooning and swarming technology as it relates to automobiles.

Discussion:
Extreme Programming:
Finally, XP comes to the actual programming section and makes its "extreme recommendations." Like I've said earlier, I like the idea of pair programming and I've had positive experiences with it in the past. Pair programming, is like they say, fun and a lot of bad ideas and bugs do get caught while doing it.
As much as XP likes it, I don't care much for the idea of "continuous integration." It just doesn't seem all that possible to me, especially for large projects where build time can take a day or longer. Now integrating once a day seems reasonable though.
I could stand to improve my own coding style by adhering to their simple design principles and should definitely refactor my own code more often. So I guess I'll take this as "lesson learned."
Overall, I wouldn't say that Extreme Programming is all that extreme. Really they're only advocating good coding principles.
Design of Future Things:
While interesting overall, I feel that Norman diverged from the title of his chapter "Servants of Our Machines" and rambled a good bit.
His observations on human tendencies once again prove to be the most valuable. His observations on vigilance on systems that are mostly automated raise interesting questions for transportation automation and almost imply that full automation of any kind of transportation is unfeasible due to the unexpected nature of reality, administration implications, and issues of adoption rates, despite what benefits automation in those fields could provide.
It was interesting to see that Norman essentially chose a view of technology that matched the orientation that was advocated in the Ethics of Engineering course I took last semester; namely that Technology should neither be viewed pessimistically or optimistically, but with a mixed view that acknowledges that technologies both solve and introduce new problems and that the progression of technology will continue despite lack of understanding of the resulting effects.
No comments:
Post a Comment