The Pragmatic Programmer

按有用程度 按页码先后 最新笔记

• 

  1.1 Prototypes

  Ovilia (静观己心，厚积薄发)

  The distinction is important enough to warrant repeating. Prototyping generates disposable code. Tracer code is lean but complete, and forms part of the skeleton of the final system. Think of prototyping as the reconnaissance and intelligence gathering that takes place before a single tracer bullet is fired. 主要在说Prototypes和Tracer code的区别，我的理解是，前者是为了给客户和开发者看最终效果从而... (更多)

  The distinction is important enough to warrant repeating. Prototyping generates disposable code. Tracer code is lean but complete, and forms part of the skeleton of the final system. Think of prototyping as the reconnaissance and intelligence gathering that takes place before a single tracer bullet is fired.

  主要在说Prototypes和Tracer code的区别，我的理解是，前者是为了给客户和开发者看最终效果从而统一对需求的理解，做一个比较完整的东西出来看效果，其实现可能是虚拟的（比如一个算法没有实现，直接输出一个假的结果），展示完以后完全抛弃；后者是为了打通技术关键，确定可行性，实现可能不是很高效，但是能用的，展示完以后等于制定好了框架，在这个基础上进行开发，而不是完全抛弃。

  What sorts of things might you choose to investigate with a prototype? Anything that carries risk. Anything that hasn't been tried before, or that is absolutely critical to the final system. Anything unproven, experimental, or doubtful. Anything you aren't comfortable with.

  (收起)

  2011-08-28 19:46:19   回应

  收藏

  推荐
• 

  2.8 Orthogonality

  Ovilia (静观己心，厚积薄发)

  When you bring in a toolkit (or even a library from other members of your team), ask yourself whether it imposes changes on your code that shouldn't be there. If an object persistence scheme is transparent, then it's orthogonal. If it requires you to create or access objects in a special way, then it's not. Keeping such details isolated from your code has the added benefit of making it easier to c... (更多)

  When you bring in a toolkit (or even a library from other members of your team), ask yourself whether it imposes changes on your code that shouldn't be there. If an object persistence scheme is transparent, then it's orthogonal. If it requires you to create or access objects in a special way, then it's not. Keeping such details isolated from your code has the added benefit of making it easier to change vendors in the future.

  (收起)

  2011-08-25 18:39:49   回应

  收藏

  推荐

• 

  1.1 Prototypes

  Ovilia (静观己心，厚积薄发)

  The distinction is important enough to warrant repeating. Prototyping generates disposable code. Tracer code is lean but complete, and forms part of the skeleton of the final system. Think of prototyping as the reconnaissance and intelligence gathering that takes place before a single tracer bullet is fired. 主要在说Prototypes和Tracer code的区别，我的理解是，前者是为了给客户和开发者看最终效果从而... (更多)

  The distinction is important enough to warrant repeating. Prototyping generates disposable code. Tracer code is lean but complete, and forms part of the skeleton of the final system. Think of prototyping as the reconnaissance and intelligence gathering that takes place before a single tracer bullet is fired.

  主要在说Prototypes和Tracer code的区别，我的理解是，前者是为了给客户和开发者看最终效果从而统一对需求的理解，做一个比较完整的东西出来看效果，其实现可能是虚拟的（比如一个算法没有实现，直接输出一个假的结果），展示完以后完全抛弃；后者是为了打通技术关键，确定可行性，实现可能不是很高效，但是能用的，展示完以后等于制定好了框架，在这个基础上进行开发，而不是完全抛弃。

  What sorts of things might you choose to investigate with a prototype? Anything that carries risk. Anything that hasn't been tried before, or that is absolutely critical to the final system. Anything unproven, experimental, or doubtful. Anything you aren't comfortable with.

  (收起)

  2011-08-28 19:46:19   回应

  收藏

  推荐
• 

  2.8 Orthogonality

  Ovilia (静观己心，厚积薄发)

  When you bring in a toolkit (or even a library from other members of your team), ask yourself whether it imposes changes on your code that shouldn't be there. If an object persistence scheme is transparent, then it's orthogonal. If it requires you to create or access objects in a special way, then it's not. Keeping such details isolated from your code has the added benefit of making it easier to c... (更多)

  When you bring in a toolkit (or even a library from other members of your team), ask yourself whether it imposes changes on your code that shouldn't be there. If an object persistence scheme is transparent, then it's orthogonal. If it requires you to create or access objects in a special way, then it's not. Keeping such details isolated from your code has the added benefit of making it easier to change vendors in the future.

  (收起)

  2011-08-25 18:39:49   回应

  收藏

  推荐