> This anxiety of pushing out at fix - at the risk of undoing other working functionality - ought to be addressed first. It really depends on how urgent the fi

> This anxiety of pushing out at fix - at the risk of undoing other working functionality - ought to be addressed first. It really depends on how urgent the fix is. Naturally you want the fix to be as isolated as possible so it does not regress other functionality. But even non-urgent fixes can sometimes benefit from getting pushed out following quick manual testing. For example we use Sentry.io for capturing errors in our applications and LogDNA for logging. Occassionally we'll encounter some kind of edge case where we see a spike in logged errors which blows us past our Sentry and LogDNA quotas. Pushing a fix out before the test is written can be beneficial in cases like this although yes, it's worth avoiding if possible.