Fix a bug / Write a unit test
One solid practice to have while coding is to fix a bug and at the same time write a unit test that would have uncovered it.
It is a sign of solid experience in software engineering.
The direct benefits are to avoid regressions for this bug, to ensure the fix is correct and to increase code coverage and the reliability of the test suite.
The indirect one is to promote a culture of quality and reliance on unit testing in the engineering team.
Software Engineering from the Frontlines Course on Maven
If you liked this article, I will be teaching a “Software Engineering from the Frontlines” course on Maven where I will teach hard-learned lessons I acquired developing large-scale products at companies such as Uber, Airbnb, and Microsoft.
Usually I write the unit test first, to make sure it actually finds the bug, then fix it. (Which is probably how you mean this, but clarity is good.)
Red-to-green feels so nice!