Extreme Programming Installed
Summary:
The first chapter just discusses the necessary task to be done after user stories. It is to sit down with team members and hear out and choose the simplest idea to implement. It is then followed by the concept of paired programming were two people work at one machine on the code. They then integrate it with the full project, test it, then release it. It also asks to keep the design of the code simple and avoid complex algorithms when possible. One could then also re factor in order to fix code and preserve the functions. It is also good to keep with the coding standards to avoid confusion on the code and to avoid overtime. It then finishes off focusing on paired programming where one is the driver while the other overlooks their shoulder and checks code. This produces better code and 2 programmers working together beats working separately.
Discussion:
I enjoyed going further into paired programming. That is one aspect of extreme programming I have not done. I would like to see how the process works first hand. I also enjoyed the statement about not working over 40 hours a week.
No comments:
Post a Comment