On Implementing Pull Request Feedback: A Short Story
You should never be so antsy to get your pull request that you skip the all important task of testing any changes you make. Even if the change is tiny and seemingly inconsequential there is no excuse to not quickly test that everything works as expected. This anxiousness of getting your code into master is the sign of an immature developer who would skip steps to make things go faster.
This will be a relatable story for many developers, but this part especially stood out to me. When making changes to a PR, I’m always worried about the time (and budget) those changes are taking up. But frankly, the work takes the time that it takes. Implementing and testing those changes are an essential part of that process, and skipping steps so as to not go over time on a task will only create more problems later.