Building Quality in Legacy Systems - The Art of Asking Questions
summary
Applies Gojko Adzic’s quality pyramid to a 30+-year healthcare patient‑record codebase, turning vague goals into concrete checks: automate or at least catalogue manual delivery steps, use context mapping to document integrations and team boundaries, run exploratory testing and targeted logging for cross‑subdomain flows, perform code reading to spot synchronous/multi‑threading hazards, and combine impact mapping with domain‑driven design to align features with business outcomes. The result is bigger tasks but measurable confidence that changes are deployable, useful, and aligned with customer projects like database co‑location.
AI-written summary · about
chapters (9)
- 0:00Intro
- 1:01Maslow's Hierarchy of Needs
- 1:31Maslow - Physiological Needs
- 4:38Different perspectives in the legacy system
- 5:17Delivery process related questions
- 5:53Conditions of Acceptance
- 6:42Code and product maintainability related questions
- 7:40Security and performance related questions
- 11:01Summary: Mapping of different perspectives to the software quality pyrami
related talks
33mBuilding Code Quality
18mBuilding a Culture of Code Quality
14mThinking of Quality as developer productivity tool
26mFacing the "Quality" Problem in Long-Lived Codebases
35mWhy Software Engineers Should Make Quality a Priority
43mBuild in Quality
55mZen and the Art of Code Life Cycle Maintenance
01h 00mZen and the art of life cycle maintenance