𝗧𝗲𝗹𝗹 𝗺𝗲 𝗮𝗯𝗼𝘂𝘁 𝗮 𝘁𝗶𝗺𝗲 𝘆𝗼𝘂 𝗳𝗮𝗶𝗹𝗲𝗱.
At Pelicargo, we have a routine of releasing updates every Tuesday. On the day of one such release (today), I found myself in a tight spot. I had been focused on another ticket for most of the previous week, which left me with limited time to finish a ticket scheduled for today's release. I felt like I had to rush to get it in, so I submitted a PR for review without thoroughly testing it.
As my coworkers began pulling in my PR to test it themselves, it became clear that there were several issues. My lack of testing had introduced bugs and confusion that could have been easily avoided. I realized that the time I thought I was saving by skipping the testing phase had actually led to my team spending more time on this ticket than required.
Understanding that I screwed up, I admitted to my team that I had made a mistake by requesting reviews too early. I converted the PR into a draft, addressed all the bugs and concerns, and performed the testing that I should've done earlier.
With the issues resolved and the testing completed, the review process went smoothly, and we didn’t encounter any further bugs. Today I have learned a valuable lesson: proper testing, even under tight deadlines, is crucial if you want to avoid unnecessary delays.
Great to have you on board!