Code quality as an engine of your IT business
summary
Company uses a modular, between-monolith-and-microservices architecture with semantic versioned modules and enforced PR gates (1 approver for patch, 2 for minor, 3+architect for major). That process plus static analysis (mentions Scrutinizer and code sniffer rules) and a dashboard of metrics (cyclomatic complexity, duplication, coverage) lets the team ship 60 large features in six months while doubling codebase size to ~300k+ lines without major merge conflicts; releases block if configured tech‑debt rules fail and done‑done requires customer presentation.
AI-written summary · about
chapters (17)
- 0:00Start
- 2:23Modular Approach
- 4:06Last 6 months in Spryker we
- 7:24Where are business benefits?
- 9:25High code quality/velocity over time
- 10:44Legacy code
- 11:19High quality code
- 12:37Define your rules
- 15:06Measure code quality
- 19:53Learn basics
- 22:44Upgrade to professional
- 24:38Request for change
- 25:53Code entropy
- 27:49Poor code transparency
- 29:35Indirect DRY violation
- 31:35Tooling
- 33:05Takeaways
related talks
28mSome small steps for code, One giant leap for quality
59mTechniques for writing high-quality code
43mDeliver Fast with Confidence
01h 03mBeyond the innovator’s dilemma
38mBuilding a high quality product
43mBuild in Quality
42marchitect's Guide to Managing a Code Base
18mAgile leadership and technical mastery, a harmonious alliance