> I can walk to a users computer, be shown the bug, fix and test it on my machine and deploy it in minutes. There's a few assumptions here. The first is that t

> I can walk to a users computer, be shown the bug, fix and test it on my machine and deploy it in minutes. There's a few assumptions here. The first is that the user will recognize it as a bug and call you straight away, they could try several times before realizing this, which could be time consuming. There is also your time being waste be being called over for any potential bug. And that's assuming the bug is noticeable, an edge case in your program could result in bad data being fed into another system. In that case your bug might not be noticed for months (or never) in which case trying to track down the source of the error is a much bigger problem.