Jonathan Bennett

Ever struggle with "whack-a-mole" bugs

I have a confession: I sometimes write bugs. I know, I’ve ruined your perfect image of me,

Here’s the thing: all programmers write bugs. Good programmer make sure that a bug only needs to be fixed once.

When a bug happens, the path to fix it is a simple (though sometimes very difficult) process:

  1. Replicate the issue locally.
  2. Write a failing test with the expected outcome.
  3. Get the failing test to pass.
  4. Review changes and improve your code.

By always writing a test for bugs, you can move forward with confidence, knowing that the issue is fixed and won’t happen again in the future.

Are you doing regression testing in your projects?