Tidy First

Messy code is a nuisance. "Tidying" code, to make it more readable, requires breaking it up into manageable sections. In this practical guide, author Kent Beck, creator of Extreme Programming and pioneer of software patterns, suggests when and where you might apply tidyings to improve your code while keeping the overall structure of the system in mind.

Instead of trying to mast...

(展开全部)

Messy code is a nuisance. "Tidying" code, to make it more readable, requires breaking it up into manageable sections. In this practical guide, author Kent Beck, creator of Extreme Programming and pioneer of software patterns, suggests when and where you might apply tidyings to improve your code while keeping the overall structure of the system in mind.

Instead of trying to master tidying all at once, this book lets you try out a few examples that make sense for your problem. If you have a big function containing many lines of code, you'll learn how to logically divide it into smaller chunks. Along the way, you'll learn the theory behind software design: coupling, cohesion, discounted cash flows, and optionality.

This book helps you:

* Understand the basic theory of how software design works and the forces that act on it

* Explore the difference between changes to a system's behavior and changes to its structure

* Improve your programming experience by sometimes tidying first and sometimes tidying after

* Learn how to make large changes in small, safe steps

* Approach software design as an exercise in human relationships

Kent Beck is a programmer, creator of Extreme Programming, pioneer of software patterns, coauthor of JUnit, rediscoverer of Test-Driven Development, and observer of 3X: Explore/Expand/Extract. Beck is also alphabetically the first signatory of the Agile Manifesto. He lives in San Francisco, California, and he is Chief Scientist at Mechanical Orchard, teaching skills to help gee...

(展开全部)

Kent Beck is a programmer, creator of Extreme Programming, pioneer of software patterns, coauthor of JUnit, rediscoverer of Test-Driven Development, and observer of 3X: Explore/Expand/Extract. Beck is also alphabetically the first signatory of the Agile Manifesto. He lives in San Francisco, California, and he is Chief Scientist at Mechanical Orchard, teaching skills to help geeks feel safe in the world.

Readers can connect with or follow him via:

Facebook: https://www.facebook.com/kentlbeck

Twitter: https://twitter.com/KentBeck

LinkedIn: https://www.linkedin.com/in/kentbeck

Medium: https://medium.com/@kentbeck_7670

Website: https://www.kentbeck.com

Foreword
Preface
What Is Tidy First?
Audience
What You Will Learn
Structure of the Book
· · · · · · (更多)

Foreword
Preface
What Is Tidy First?
Audience
What You Will Learn
Structure of the Book
Why “Empirical” Software Design?
How I Came to Write Tidy First?
O’Reilly Online Learning
How to Contact Us
Acknowledgments
Introduction
I. Tidyings
1. Guard Clauses
2. Dead Code
3. Normalize Symmetries
4. New Interface, Old Implementation
5. Reading Order
6. Cohesion Order
7. Move Declaration and 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
II. Managing
16. Separate Tidying
17. Chaining
Conclusion
18. Batch Sizes
19. Rhythm
20. Getting Untangled
21. First, After, Later, Never
Never
Later
After
First
Summary
III. Theory
22. Beneficially Relating Elements
Elements
Relating
Beneficially
Beneficially Relating Elements
23. Structure and Behavior
24. Economics: Time Value and Optionality
25. A Dollar Today > A Dollar Tomorrow
26. Options
27. Options Versus Cash Flows
28. Reversible Structure Changes
29. Coupling
30. Constantine’s Equivalence
31. Coupling Versus Decoupling
32. Cohesion
33. Conclusion
Appendix. Annotated Reading List and References
Index
About the Author
· · · · · · (收起)