Skip to content

Commit

Permalink
Refactor mention of evolutionary coding methods with link
Browse files Browse the repository at this point in the history
  • Loading branch information
DevOpsCraftsman committed Jul 18, 2023
1 parent cc326ac commit f0e8c2c
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion content/Journey/_index.md
Original file line number Diff line number Diff line change
Expand Up @@ -68,7 +68,7 @@ Teams are not good at testing initially for the same reason they aren't good at

### Individual tasks are too big

CI means we are integrating partially completed features continuously. TDD helps us learn how to decompose tasks into very small, releasable changes that do not break existing behaviors. However, the initial habit is often to wait to integrate changes until they are "complete". This results in large change-sets that are more difficult to code review. This makes code review take more time, requires more re-work, and reduces the ability of the reviewer to spot problems. Techniques such as [Feature Toggles](https://martinfowler.com/bliki/FeatureToggle.html) or [Keystone Interfaces](https://martinfowler.com/bliki/KeystoneInterface.html) allow the release of incomplete features until they are ready and allow us to drive down the size of changes. By focusing as a team to decompose tasks into hours of work rather than days and using engineering techniques to control release, we have improved clarity, smaller change-sets, and higher quality.
CI means we are integrating partially completed features continuously. TDD helps us learn how to decompose tasks into very small, releasable changes that do not break existing behaviors. However, the initial habit is often to wait to integrate changes until they are "complete". This results in large change-sets that are more difficult to code review. This makes code review take more time, requires more re-work, and reduces the ability of the reviewer to spot problems. [Evolutionary coding methods](../MinimumCD#evolutionary-coding-methods) allow the release of incomplete features until they are ready and allow us to drive down the size of changes. By focusing as a team to decompose tasks into hours of work rather than days and using engineering techniques to control release, we have improved clarity, smaller change-sets, and higher quality.

### Stories are too big & lack testable acceptance criteria

Expand Down

0 comments on commit f0e8c2c

Please sign in to comment.