读《高效程序员的45个习惯：敏捷开发修炼之道》笔记

延伸阅读列表（书）：

敏捷软件开发：原则、模式与实践  http://book.douban.com/subject/2347793/  现在能买到清华老版，人邮新版有C#注释版。

程序员修炼之道  http://book.douban.com/subject/1152111/  http://book.douban.com/subject/1119873/  影印版买不到了，刘江说译本翻译得不错。

项目管理修炼之道  http://book.douban.com/subject/4058336/  购买。

项目自动化之道  http://book.douban.com/subject/1449002/  网店全面缺货。

Agile and Iterative Development: A manager's Guide  http://book.douban.com/subject/1801394/  影印版买不到了，电子工业的译本。

My Job Went to India: 52 Ways to Save Your Job  http://wenku.baidu.com/view/946033a20029bd64783e2cb7.html

Passionate Programmer  http://book.douban.com/subject/3729539/

解析极限编程  http://book.douban.com/subject/1127939/  http://book.douban.com/subject/1790225/

Ship It!  http://book.douban.com/subject/1433491/

Behind Closed Doors  http://book.douban.com/subject/1433489/

延伸阅读列表（文章、链接）：

http://blogs.pragprog.com/cgi-bin/progdave.cgi/Random/FishBowl.rdoc  在Dave Thomas的博客上没有找到FishBowl这篇。

Is Design Dead?  www.martinfowler.com/articles/designDead.html

Continuous Integration  www.martinfowler.com/articles/continuousIntegration.html

xprogramming.com/software.htm

The Paperboy, The Wallet, and The Law Of Demeter  www.javaguy.org/papers/demeter.pdf

Who Needs an Architect?  http://martinfowler.com/ieeeSoftware/whoNeedsArchitect.pdf

Information Radiator  c2.com/cgi-bin/wiki?InformationRadiator

Agile Developer下载页面  http://www.agiledeveloper.com/download.aspx

Andy的博客  http://toolshed.com/blog

Anthill，控制构建过程的工具  http://www.urbancode.com/projects/anthill/default.jsp

Damage Control，用Ruby on Rails编写的持续集成工具  http://dev.buildpatterns.com/trac/wiki/DamageControl

Dependency Inversion  http://c2.com/cgi/wiki?DependencyInversionPrinciple

Principles of Object Oriented Design  http://c2.com/cgi/wiki?PrinciplesOfObjectOrientedDesign

Ted Neward对框架的讨论  http://www.neward.net/ted/weblog/index.jsp?date=20041003#1096871640048

Open Closed Principle  http://objectmentor.com/resources/articles/ocp.pdf

Open Closed Principle  http://c2.com/cgi/wiki?OpenClosedPrinciple

Single Responsibility Principle  http://c2.com/cgi-bin/wiki?SingleResponsibilityPrinciple

Capers Jones对250个软件项目成败的分析  http://www.stsc.hill.af.mil/crosstalk/2004/10/0410Jones.html

Test Driven Development  http://c2.com/cgi/wiki?TestDrivenDevelopment

the end of software engineering  http://alistair.cockburn.us/crystal/articles/eoseatsoecg/theendofsoftwareengineering

Why Your Code Sucks  http://www.artima.com/weblogs/viewpost.jsp?thread=71730

You Arent Gonna Need It  http://c2.com/cgi/wiki?YouArentGonnaNeedIt

摘抄：

反馈是敏捷的基础，要不断地使用反馈进行自我调整和完善；同时，要先解决困难的问题，把简单的问题留到最后。

让我们骄傲的应该是解决了问题，而不是比较出谁的主意更好。

记录客户做出的决定，并注明原因。可以使用工程师的工作日志，wiki，邮件或问题跟踪数据库。

“为什么”是一个非常好的问题。理解一个问题的时候，需要渐次问5个以上的“为什么”。不能只满足于别人告诉你的表面现象，要不停地提问直到你明白问题的根源。

找人询问任何相关的问题时，让他们耐心地回答你的问题，这是你的职责。

方案的花费不应该高于要解决的问题，否则就是一次失败的投资。

新技术就应该像是新的工具，可以帮助你更好地工作，它自己不应该成为你的工作。

Checked-in code is always ready for action.

提交文件应该与一个特定的任务或是一个bug的解决相关。而且应该是同时提交相关的文件。

错误：

P101 L19 coffeeShop.PlaceOrder(CoffeeCupSize.Largxe); -> coffeeShop.PlaceOrder(CoffeeCupSize.Large);