leave code better than you found it (boy scout rule)

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

https://martinfowler.com/bliki/RefinementCodeReview.html
https://go.dev/blog/examples

Join this channel to get access to perks:
https://www.youtube.com/channel/UC9H0HzpKf5JlazkADWnW1Jw/join

My other corners of the Internet:
https://mastodon.social/@bashbunni
https://github.com/bashbunni
https://twitter.com/sudobunni
https://twitch.tv/bashbunni (not very active atm)
https://discord.com/invite/Y3vbKS4K9j

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

Видео leave code better than you found it (boy scout rule) канала bashbunni