Evidence from change history
On This Lesson 4 topics
This lesson is planned. The outline below lists the topics it will cover. The full lesson has not been published yet.
In this lesson
use Git history to see what really changes together.
Planned topics
- Files that change in the same commit or PR show change coupling.
- Count co-changes across a time window; ignore noise (formatting, dependency bumps).
- Cross-service co-change means the boundary does not match the change pattern.
- History shows what is; it does not show what should be; combine with domain knowledge.
Draft outline details
Demonstration
a table: pair of modules, co-change count, percent of commits, interpretation.
Check your understanding
What does frequent co-change across two services suggest?
Show answer
The boundary may be in the wrong place or they should be merged.
Practice
Apply this lesson with the module's lab, exercises and quiz.
Marking a lesson complete is optional and you can undo it any time. Your progress stays in this browser.