1. Rush to change the code
  2. Make some tests in the ui to check that it disappears
  3. Rush to deploy
  4. Fix the related bugs (due to regression) declared by users 24h later
  5. Go back to 1 until a churn (due to frustration)
  6. Take time to do a full QA and engage product team / domain experts before you ship again.

Of course you can be lucky with some easy to fix situations, but this is not a sustainable way and methodology.
It may last few weeks/months and have very bad business impacts.

How to fix a bug efficiently ?

  1. Add the buggy scenario to your test suite : unit test first, if green then integration, and if it is still green then e2e.

  2. Once you got the red test, ask clarification from domain experts and product team. (Bugs can be related to poor businesses logic)

  3. Write the necessary code to fix it as expected in the most maintainable form and share the change with your peers.

  4. Enjoy feedback from your satisfied clients.

This can be very fast and depends on the team reactivity.

Don’t let the « illusion » of going fast tricks you!