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,314,088writing, 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
Top 20 Digital Health Trends For The Near Future
Dr. Bertalan MeskoDigital technology could help transform unsustainable healthcare systems, provide cheaper, faster, and more effective solutions for diseases – and could lead to healthier individuals living in healthier communities.
In this book, we analyze the top 20 trends shaping the future of healthcare, and what they all look like in practice.
- #2
Continuous Delivery Pipelines
Dave FarleyThis practical handbook provides a step-by-step guide for you to get the best continuous delivery pipeline for your software.
- #3
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!
- #4
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.
- #5
Introducing EventStorming
Alberto BrandoliniThe deepest tutorial and explanation about EventStorming, straight from the inventor.
- #6
The Hundred-Page Machine Learning Book
Andriy BurkovEverything you really need to know in Machine Learning in a hundred pages.
- #7
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.
- #8
CCIE Service Provider Version 4 Written and Lab Exam Comprehensive Guide
Nicholas RussoThe service provider landscape has changed rapidly over the past several years. Networking vendors are continuing to propose new standards, techniques, and procedures for overcoming new challenges while concurrently reducing costs and delivering new services. Cisco has recently updated the CCIE Service Provider track to reflect these changes; this book represents the author's personal journey in achieving that certification.
- #9
Hacking your way around in Emacs
Marcin BorkowskiThis is an intermediate textbook on Emacs Lisp. Learn how to write you own commands and make Emacs truly your editor, suited to your needs!
- #10
C++ Best Practices
Jason TurnerLevel up your C++, get the tools working for you, eliminate common problems, and move on to more exciting things!
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
CCIE Service Provider Ultimate Study Bundle
2 Books
Piotr Jablonski, Lukasz Bromirski, and Nick Russo have joined forces to deliver the only CCIE Service Provider training resource you'll ever need. This bundle contains a detailed and challenging collection of workbook labs, plus an extensively detailed technical reference guide. All of us have earned the CCIE Service Provider certification... - #4
9 Books-Bundle: Shut Up and Code!
9 Books
"Shut up and code." Laughter in the audience. The hacker had just plugged in his notebook and started sharing his screen to present his super-smart Python script. "Shut up and code" The letters written in a white literal coding font on black background was the hackers' home screen background mantra. At the time, I was a first-year computer... - #6
Practical Foundations of Debugging, Disassembling, Reversing
2 Books
The books teach assembly language foundations necessary for deep debugging and program reconstruction. They are useful for: - Software technical support and escalation engineers; - Software engineers coming from different backgrounds, OS, and programming/debugging environments; - Software testers; - C/C++ software engineers without assembly... - #7
Software Architecture and Design Practice Reference
2 Books
Dive deeper in Software Architecture with the Design Practice Reference. Learn all about software architecture and design from the books in this bundle:Software Architecture covers topics from quality attributes to designing and modeling components, interfaces, connectors, and containers, all the way to services and microservices. The Design... - #10
Mastering Containers
2 Books
Docker and Kubernetes are taking the world by storm! These books will get you up-to-speed fast! Docker Deep Dive is over 400 pages long, and covers all objectives on the Docker Certified Associate exam.The Kubernetes Book includes everything you need to get up and running with Kubernetes!
