👨‍💻
Software Engineering
Tidy First?: A Personal Exercise in Empirical Software Design
Tidy First?: A Personal Exercise in Empirical Software Design
  • Tidy First?
  • Foreword
  • Preface
  • Part 1: Tidyings
    • 1: Guard Clauses
    • 2: Dead Code
    • 3: Normalize Symmetries
    • 4: New Interface, Old Implementation
    • 5: Reading Order
    • 6: Cohesion Order
    • 7: Move Declaration & Initialization Together
    • 8: Explaining Variables
    • 9: Explaining Constants
    • 10: Explicit Parameters
    • 11: Chunk Statements
    • 12: Extract Helper
    • 13: One Pile
    • 14: Explaining Comments
    • 15: Delete Redundant Comments
  • Part 2: Managing
    • Coming soon
  • Part 3: Theory
    • Coming soon
Powered by GitBook
On this page

Foreword

By Larry Constantine

This Book is for Professional Programmers - developers with a deep & geeky interest in their craft and in improving their work in small ways with big payoffs.

Practicing software developers often pay scant attention to theory, but this book mixes practice & theory making it both readable & practical.

In theory, this is no difference between theory & practice while in practice there is. ~ Benjamin Brewster

This is a profession that hinges on getting the details right.

The complexity of code depends on how it is organized into parts, on how coupled those parts are with each other, and how cohesive the parts are in themselves.

Coupling and cohesion are simply measures of the complexity of computer code from the perspective of human beings trying to understand the code. Coupling and cohesion are really about how your brain details with complicated systems.

PreviousTidy First?NextPreface

Last updated 23 days ago