Git Driven Refactoring
summary
Use Git history, diffs and PRs to find concrete refactors: group commits into topics to reveal single‑responsibility violations, look for red in diffs when adding features to spot open/closed problems, add GitHub webhooks or linters to flag Liskov and dependency issues, and use git log and git blame to count how often code changes so you prioritize high‑impact cleanup. The workflow relies on disciplined commit messages and consistent style and results in smaller, injected dependencies and easier maintenance.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 7:50Single Responsibility Principle
- 17:44Liskov Substitution Principle
- 21:22Code Quality
- 22:02Interface Segregation
- 23:34Active Record Relation
- 26:22Balance
- 27:34Dependency Injection
- 29:24Recap
