Refinement code review means continuously improving existing code, not just reviewing new contributions in pre-integration workflows like pull requests. While my strategy is a bit different than Martin Fowler's, I have noticed an improvement in the overall hygiene of the repos I work on since starting this habit. In this video I'll walk you through how I leave the code better than I found it. As I grow as a developer, I'll share more ways I improve codebases over time :) In the meantime, please let me know what you think and how you tidy up! -bashbunni Join this channel to get access to perks: My other corners of the Internet: @bashbunni (not very active atm) Chapters: 0:00 what we're talkin' about 0:58 clarifying misunderstandings 1:54 examples + goated Golang feature 2:37 considerations when reviewing PRs 3:46 code coverage 4:12 plz respond 4:26 let's be real