Some small steps for code, One giant leap for quality
summary
Concrete steps: keep a visible tech-debt tracker (markdown or Jira epic) with issue comments linking to offending files; run linters like ESLint and Prettier and platform scanners such as SonarQube plus IDE extensions; make code reviews demand specific, actionable feedback to reduce bus‑factor risk; split testing boundaries (unit front-end/back-end, integration where needed), add performance scenarios, and gate merges with CI/CD gated tests. Agree team-wide conventions (e.g. move to TypeScript, prefer functional patterns) and enforce them in reviews.
AI-written summary · about
chapters (9)
- 0:00Introduction and welcome
- 1:48Code quality assumptions
- 2:52Code quality is a team effort
- 4:18Managing technical debt
- 9:18Tools for code quality
- 11:25Optimizing code reviews
- 17:26Reevaluating testing philosophy
- 22:03Team code quality agreements
- 27:01Conclusion and Q&A
related talks
59mTechniques for writing high-quality code
33mBuilding Code Quality
43mBuild in Quality
17mHow to Ensure Code Quality and Consistency in Distributed Teams
18mBuilding a Culture of Code Quality
43mScalable Best Practices for Your Development Team
17mHow to deal with technical debt in fast-paced environment
43mCode quality as an engine of your IT business