Agile Technical Practices Distilled
Agile Technical Practices Distilled
A Journey Toward Mastering Software Design
About the Book
The authors of the book have been working as software developers and coaches for years, accumulating more then half a century of experience. During this period working in the trenches of teaching software design we created lots of content and shared many stories of real professional life among us. From the feedback we had, we thought it would be a good idea to organize all the information in a single place, following a logical sequence, creating a sort of learning journey. We touch all the principles we consider important to master, dropping too many details. In our profession the information are far too many to be all memorized, let alone mastered. The ability to select what to focus on is maybe more important then the ability of learning itself. We all are very excited to be able to share with you our personal selection of content and the lessons we learned the hard way. We genuinely hope that at the end of it you will find some new ideas for improving your Software Design skills, the relationship within your team and your business as well.
About the Authors
About the Contributors
Table of Contents
-
Introduction
-
AGILE TECHNICAL PRACTICES
- Is this book for me?
- Why we wrote this book
- Why distilled?
- What are Agile Technical Practices?
- Rules, principles and values
- How this book is organized
- How to get the most out of this book
- Resources
-
AGILE TECHNICAL PRACTICES
-
First steps
-
PAIR PROGRAMMING
- What is pair programming?
- Roles
- Driver/Navigator switch techniques
- Breaks
- Katas
- When should I move to the next chapter?
- Resources
-
CLASSIC TDD I – TEST-DRIVEN DEVELOPMENT
- Classic TDD
- The three laws of TDD
- Refactoring and the Rule of Three – baby steps
- Three methods of moving forward in TDD
- Degrees of freedom
- Naming tests
- A test name pattern
- Katas
- More katas
- Great habits
- Classic TDD flow
- Where are we in the big picture of OO software design?
- When should I move to the next chapter?
- Resources
-
CLASSIC TDD II
- Writing the assertion first and working backward
- Organizing your test in arrange, act and assert blocks
- Unit test principles
- Katas
- Great habits
- Classic TDD flow
- Where are we in the big picture of OO software design?
- When should I move to the next chapter?
- Resources
-
CLASSIC TDD III – TRANSFORMATION PRIORITY PREMISE
- Kata
- TPP – Defining obvious implementation
- Katas
- Great habits
- Classic TDD flow
- Where are we in the big picture of OO software design?
- When should I move to the next chapter?
- Resources
-
DESIGN I – OBJECT CALISTHENICS
- It’s the design…
- Kata
- Object calisthenics – 10 steps for better software design
- Heuristics
- Katas
- Great habits
- Classic TDD flow
- Where are we in the big picture of OO software design?
- When should I move to the next chapter?
- Resources
-
PAIR PROGRAMMING
-
Walking
-
DESIGN II - REFACTORING
- When to refactor (for now)
- Main refactors
- IDE agility (a.k.a. know your shortcuts)
- Kata
- Refactor 80-20 rule
- Refactoring guidelines
- Kata
- Parallel change (or expand, migrate and contract)
- Kata
- Great habits
- When should I move to the next chapter?
- Resources
-
DESIGN III – CODE SMELLS
- Design smells
- Code smells
- Highlighted code smells
- Object calisthenics preventing code smells
- When to refactor (extended for code smells)
- Refactor code smells
- Kata
- Great habits
- Classic TDD flow
- The big picture
- When should I move to the next chapter?
- Resources
-
TEST DOUBLES
- Principles
- Different types of Test Doubles
- Test Doubles guidelines
- Katas
- Great habits
- When should I move to the next chapter?
- Resources
-
TESTING LEGACY CODE
- Breaking dependencies using a seam
- Characterization tests
- Kata
- Golden Master
- Kata
- Approval Tests by Llewellyn Falco
- Revisiting the refactoring guidelines
- Kata
- Conclusions
- Great habits
- When should I move to the next chapter?
- Resources
-
DESIGN IV – DESIGN PATTERNS
- Design patterns advantages
- Design patterns pitfalls
- Quick reference catalogue
- Revisiting the refactoring guidelines
- Kata
- Great habits
- When should I move to the next chapter?
- Resources
-
DESIGN II - REFACTORING
-
Running
-
DESIGN V – COHESION AND COUPLING
- Coupling
- Cohesion
- Katas
- When to refactor (extended for Cohesion/Coupling)
- Classic TDD flow
- The big picture
- When should I move to the next chapter?
- Resources
-
DESIGN VI – SOLID PRINCIPLES++
- Single Responsibility Principle
- Open/Closed Principle
- Liskov Substitution Principle
- Interface Segregation Principle
- Dependency Inversion Principle
- Balanced Abstraction Principle
- Principle of Least Astonishment (a.k.a. WTF principle)
- Kata
- When to refactor (extended for SOLID principles)
- Classic TDD flow
- The big picture
- When should I move to the next chapter?
- Resources
-
DESIGN VII - CONNASCENCE
- Definition
- Dimensions
- Connascence of Name and Type (CoN and CoT)
- Connascence of Position (CoP)
- Connascence of Value (CoV)
- Connascence of Meaning (or Convention) (CoM)
- Connascence of Algorithm (CoA)
- Connascence of Execution Order (CoEO)
- Connascence of Timing (CoTm)
- Connascence of Identity (CoI)
- Connascence of Manual Task (CoMT)
- Classic TDD flow
- The big picture
- When should I move to the next chapter?
- Resources
-
DESIGN VIII – THE FOUR ELEMENTS OF SIMPLE DESIGN
- What are the four elements of simple design?
- What does each element mean?
- Alternative definitions of simple design
- Our personal definitions of simple design
- Kata
- Classic TDD flow
- The big picture
- When should I move to the next chapter?
- Resources
-
DESIGN IX - CONCLUSION
- Cohesion and Coupling as forces
- The 3 Cs of design: from Cohesion and Coupling to Connascence
- Systems Entropy
- The big picture
- Resources
-
DESIGN V – COHESION AND COUPLING
-
Flying
-
OUTSIDE-IN DEVELOPMENT
- Classic TDD approach
- Acceptance tests
- Test boundaries
- Double loop TDD
- The Outside-In approach
- Outside-In TDD: London school
- The direction of dependencies
- Should I use classic TDD or Outside-In TDD?
- Kata
- The big picture
- Great habits
- Resources
-
BEHAVIOR-DRIVEN DEVELOPMENT (A.K.A. LOVE YOUR REQUIREMENTS)
- Poka-yoke
- Mistakes versus defects: feedback is the cure (again)
- Bugs and communication
- User stories
- Behavior-Driven Development
- Acceptance Tests done right
- Boundaries
- The walking skeleton
- Kata
- Resources
-
UNDERSTAND THE BUSINESS
- Knowledge versus understanding
- Theory of Constraints
- Domain-Driven Design: What domain?
- Beyond requirements: knowledge crunching
- Value stream and domain events
- Bounded contexts and communication
- Business and DevOps
- System Thinking and Sociotechnical organizations
- Resources
-
THE STORY OF TEAM C
- Terraforming
- Team building
- The backlog: crunching knowledge for breakfast
- Cracking on
- From forming to performing
- Outside-In ATDD with optional unit tests
- The green flag
- The moral of the story
-
CONCLUSION
- The human factor
- Team play
- Bounded rationality and knowledge sharing
- Resources
-
OUTSIDE-IN DEVELOPMENT
-
Appendices
- THE 12 AGILE PRINCIPLES
-
PopcornFlow by Claudio Perrone
- The 7-steps decision cycle
- The principles
- Who can benefit from PopcornFlow
- Resources
-
EventStorming by Alberto Brandolini
- Silos and value stream
- The importance of learning
- The EventStorming approach
- The workshop: a quick overview
- Different flavors of EventStorming
- Complex Systems and proven solutions
- Resources
-
License: CyberDojo
- About CyberDojo Foundation exercises
- Web resources
-
SAMPLE SOLUTIONS
- Sample solutions: FizzBuzz in Clojure
- Sample solutions: Fibonacci sequence in C++
- Sample solutions: Roman numerals in C#
- Sample solutions: TicTacToe in Swift (partial solution)
- Sample solutions: Connecting code smells with Cohesion/Coupling
- Sample solutions: Connecting object calisthenics with code smells and Cohesion/Coupling
- Sample solutions: Connecting Cohesion / Coupling and SOLID principles
-
ABOUT THE AUTHORS
- Pedro
- Marco
- Alessandro
- Personalized coaching
- FEEDBACK PLEASE
- Notes
Authors have earned$10,089,287writing, publishing and selling on Leanpub, earning 80% royalties while saving up to 25 million pounds of CO2 and up to 46,000 trees.
Learn more about writing on Leanpub
The Leanpub 45-day 100% Happiness Guarantee
Within 45 days of purchase you can get a 100% refund on any Leanpub purchase, in two clicks.
See full terms
Free Updates. DRM Free.
If you buy a Leanpub book, you get free updates for as long as the author updates the book! Many authors use Leanpub to publish their books in-progress, while they are writing them. All readers get free updates, regardless of when they bought the book or how much they paid (including free).
Most Leanpub books are available in PDF (for computers), EPUB (for phones and tablets) and MOBI (for Kindle). The formats that a book includes are shown at the top right corner of this page.
Finally, Leanpub books don't have any DRM copy-protection nonsense, so you can easily read them on any supported device.
Learn more about Leanpub's ebook formats and where to read them
Top Books
- #1
C++20
Rainer GrimmC++20 is the next big C++ standard after C++11. As C++11 did it, C++20 changes the way we program modern C++. This change is, in particular, due to the big four of C++20: ranges, coroutines, concepts, and modules.
The book is almost daily updated. These incremental updates ease my interaction with the proofreaders.
- #2
A Guide to Artificial Intelligence in Healthcare
Dr. Bertalan MeskoCan we stay human in the age of A.I.? To go even further, can we grow in humanity, can we shape a more humane, more equitable and sustainable healthcare? This e-book aims to prepare healthcare and medical professionals for the era of human-machine collaboration. Read our guide to understanding, anticipating and controlling artificial intelligence.
- #3
C++ Best Practices
Jason TurnerLevel up your C++, get the tools working for you, eliminate common problems, and move on to more exciting things!
- #4
Atomic Kotlin
Bruce Eckel and Svetlana IsakovaFor both beginning and experienced programmers! From the author of the multi-award-winning Thinking in C++ and Thinking in Java together with a member of the Kotlin language team comes a book that breaks the concepts into small, easy-to-digest "atoms," along with exercises supported by hints and solutions directly inside IntelliJ IDEA!
- #5
Sockets and Pipes
Type ClassesSockets and Pipes is not an introduction to Haskell; it is an introduction to writing software in Haskell. Using a handful of everyday Haskell libraries, this book walks through reading the HTTP specification and implementing it to create a web server.
- #6
Introducing EventStorming
Alberto BrandoliniThe deepest tutorial and explanation about EventStorming, straight from the inventor.
- #7
node-opcua by example
Etienne RossignonGet the best out of node-opcua through a set of documented examples by the author himself that will allow you to create stunning OPCUA Servers or Clients.
- #8
Ansible for DevOps
Jeff GeerlingAnsible is a simple, but powerful, server and configuration management tool. Learn to use Ansible effectively, whether you manage one server—or thousands.
- #9
Functional Design and Architecture
Alexander GraninSoftware Design in Functional Programming, Design Patterns and Practices, Methodologies and Application Architectures. How to build real software in Haskell with less efforts and low risks. The first complete source of knowledge.
- #10
Composing Software
Eric ElliottAll software design is composition: the act of breaking complex problems down into smaller problems and composing those solutions. Most developers have a limited understanding of compositional techniques. It's time for that to change.
Top Bundles
- #1
Software Architecture for Developers: Volumes 1 & 2 - Technical leadership and communication
2 Books
"Software Architecture for Developers" is a practical and pragmatic guide to modern, lightweight software architecture, specifically aimed at developers. You'll learn:The essence of software architecture.Why the software architecture role should include coding, coaching and collaboration.The things that you really need to think about before... - #2
All the Books of The Medical Futurist
6 Books
We put together the most popular books from The Medical Futurist to provide a clear picture about the major trends shaping the future of medicine and healthcare. Digital health technologies, artificial intelligence, the future of 20 medical specialties, big pharma, data privacy, digital health investments and how technology giants such as Amazon... - #3
PowerShell
3 Books
Buy every PowerShell book from Adam Bertram at a 20% discount! - #4
Cisco CCNA 200-301 Complet
4 Books
Ce lot comprend les quatre volumes du guide préparation à l'examen de certification Cisco CCNA 200-301. - #5
Linux Administration Complet
4 Books
Ce lot comprend les quatre volumes du Guide Linux Administration :Linux Administration, Volume 1, Administration fondamentale : Guide pratique de préparation aux examens de certification LPIC 1, Linux Essentials, RHCSA et LFCS. Administration fondamentale. Introduction à Linux. Le Shell. Traitement du texte. Arborescence de fichiers. Sécurité... - #6
Modern C++ by Nicolai Josuttis
2 Books
- #7
Django for Beginners/APIs/Professionals
3 Books
- #8
Learn Git, Bash, and Terraform the Hard Way
3 Books
Learn Git, Bash and Terraform using the Hard Way method.These technologies are essential tools in the DevOps armoury. These books walk you through their features and subtleties in a simple, gradual way that reinforces learning rather than baffling you with theory. - #9
Software Architecture and Beautiful APIs
2 Books
There is no better way to learn how to design good APIs than to look at many existing examples, complementing the Software Architecture theory on API design. - #10
Digital Future of Healthcare and Pharma
3 Books
These three popular e-books from The Medical Futurist describes how digital health technologies will shape the future of health, healthcare, medicine and pharma with exciting infographics in a digestible format.
