Code Review of Senior Python Engineers
summary
Six concrete takeaways: insist on 95–100% coverage for key projects so reviewers can rely on tests; enforce CI/CD with GitHub Actions or Jenkins to catch deploy and rollback problems early; run static checks like fake age and Sonar Cube to surface unused imports, mutable-defaults, and lambda-in-loop bugs; require design-review templates and documentation linked from pull requests; measure whether templates and automation actually reduce review time and production incidents.
AI-written summary · about
chapters (29)
- 0:00Introduction
- 0:32Agenda
- 2:22Introducing Chris
- 4:39Comments
- 5:42Comparing Code
- 6:41Key Points
- 8:34Dental Python
- 8:51Frozen Sandwich
- 9:11Diversity
- 9:42Fake age
- 10:04Git Commit
- 10:35Python Errors
- 11:16Real case
- 11:46No paper
- 13:40Documentation
- 14:09Improvement Plan
- 14:39Plan B
- 16:25Python Documentation
- 17:01Jenkins
- 17:55CI
- 18:14Pipeline
- 18:47Essential Point
- 19:07Cold Coverage
- 20:05Tools
- 20:25Pool Request
- 21:29AI Cancer
- 21:47Python Terminology
- 23:05Teamwork
- 24:29Conclusion
related talks
40mCode Review Skills for Pythonistas
18mHow To Review Someone's Code While Not Being A Jerk!
21mMaking the Most Out of Code Reviews
41mCracking the Code Review from Guesswork to Automated Guidance
43mCode Review, you said?
40mCode Review - How to Do It Better?
53mCode Review Beyond Code Style
23mDrama-Free Code Review!