Prefactoring 

1 2 3 4

• 1. Prefactoring

• 2. Table of Contents

• 3. Copyright

• 4. Dedication

  Dedication

• 5. Preface

  Preface

• 6. Everybody Is Different

  Everybody Is Different

• 7. The Design Example

  The Design Example

• 8. Audience

  Audience

• 9. Contents of This Book

  Contents of This Book

• 10. The Cover

  The Cover

• 11. Conventions Used in This Book

  Conventions Used in This Book

• 12. Using Code Examples

  Using Code Examples

• 13. Comments and Questions

  Comments and Questions

• 14. Safari Enabled

  Safari Enabled

• 15. Acknowledgments

  Acknowledgments

• 16. Chapter One. Introduction to Prefactoring

  Chapter One. Introduction to Prefactoring

• 17. 1.1. What Is Prefactoring?

  1.1. What Is Prefactoring?

• 18. 1.2. The Three Extremes

  1.2. The Three Extremes

• 19. 1.3. The Guidelines Explored

  EXCEPTIONAL GUIDELINE BACKPACKING CONTEXT WHAT SAIL AND BOARD TO USE TODAY 1.3. The Guidelines Explored

• 20. 1.4. The Context for This Book

  AGILE DEVELOPMENT 1.4. The Context for This Book

• 21. Chapter Two. The System in So Many Words

  Chapter Two. The System in So Many Words

• 22. 2.1. Meet Sam

  2.1. Meet Sam

• 23. 2.2. Reinvention Avoidance

  DON T REINVENT THE WHEEL 2.2. Reinvention Avoidance

• 24. 2.3. What s in a Name?

  A ROSE BY ANY OTHER NAME IS NOT A ROSE AIRLINE FLIGHTS 2.3. What s in a Name?

• 25. 2.4. Splitters Versus Lumpers

  SPLITTERS CAN BE LUMPED MORE EASILY THAN LUMPERS CAN BE SPLIT 2.4. Splitters Versus Lumpers

• 26. 2.5. Clumping

  CLUMP DATA SO THAT THERE IS LESS TO THINK ABOUT 2.5. Clumping

• 27. 2.6. Abstracting

  when you re abstract be abstract all the way Never let a constant slip into code

• 28. 2.7. Prototypes Are Worth a Thousand Words

  PROTOTYPES ARE WORTH A THOUSAND WORDS 2.7. Prototypes Are Worth a Thousand Words

• 29. Chapter Three. General Development Issues

  Chapter Three. General Development Issues

• 30. 3.1. Start with the Big Picture

  THINK ABOUT THE BIG PICTURE 3.1. Start with the Big Picture

• 31. 3.2. Interface Contracts

  FINDING YOUR WAY IN THE DARK CREATE INTERFACE CONTRACTS 3.2. Interface Contracts

• 32. 3.3. Validation

  VALIDATE VALIDATE VALIDATE 3.3. Validation

• 33. 3.4. Code Communicates

  COMMUNICATE WITH YOUR CODE EXPLICITNESS BEATS IMPLICITNESS A FEW MORE WORDS GIVE MEANING READABILITY OR RDBLTY? 3.4. Code Communicates

• 34. 3.5. Consistency Is Simplicity

  CONSISTENCY IS SIMPLICITY CONSISTENT FOR WHOM? 3.5. Consistency Is Simplicity

• 35. 3.6. A Prefactoring Attitude

  ADAPT A PREFACTORING ATTITUDE 3.6. A Prefactoring Attitude

• 36. 3.7. Don t Repeat Yourself

  DON T REPEAT YOURSELF (DRY) 3.7. Don t Repeat Yourself

• 37. 3.8. Documentation of Assumptions and Decisions

  DOCUMENT YOUR ASSUMPTIONS AND YOUR DECISIONS 3.8. Documentation of Assumptions and Decisions

• 38. 3.9. Dealing with Deviations and Errors

  DECIDE ON A STRATEGY TO DEAL WITH DEVIATIONS AND ERRORS WHAT S AN ERROR TO YOU? SOONER THAN LATER CAN SAVE MILES OF WALKING REPORT MEANINGFUL USER MESSAGES ORDERING PIZZA 3.9. Dealing with Deviations and Errors

• 39. 3.10. Speeding

  DON T SPEED UNTIL YOU KNOW WHERE YOU ARE GOING OSF UNIX 3.10. Speeding

• 40. 3.11. The Spreadsheet Conundrum

  THE SPREADSHEET CONUNDRUM 3.11. The Spreadsheet Conundrum

• 41. 3.12. Tools Are Tools-Use Them Wisely

  3.12. Tools Are ToolsUse Them Wisely

• 42. Chapter Four. Getting the Big Picture

  Chapter Four. Getting the Big Picture

• 43. 4.1. The Rest of the Story

  4.1. The Rest of the Story

• 44. 4.2. Process

  SAILING THE WAVES 4.2. Process

• 45. 4.3. The Initial Design

  4.3. The Initial Design

• 46. 4.4. Global Planning, Local Designing

  REPORTS CAN DEFINE THE SYSTEM PLAN GLOBALLY DEVELOP LOCALLY HIKING THE APPALACHIAN TRAIL 4.4. Global Planning Local Designing

• 47. 4.5. Testing Functionality

  IF IT CAN T BE TESTED DON T REQUIRE IT CLEAR-CUT TEST PLAN FOR TESTING THE SKYDIVING GRANDMA 4.5. Testing Functionality

• 48. 4.6. Testing Quality

  4.6. Testing Quality

• 49. 4.7. Security

  IF YOU FORGET SECURITY YOU RE NOT SECURE 4.7. Security

• 50. Chapter Five. Got Class?

  Chapter Five. Got Class?

1 2 3 4