This is a scary story, not like a horror movie, but frightening enough to give any developer the shivers. The story goes a little something like this…
A customer directs your attention to a bug you know you’ve solved, tested and shipped. You fixed it one day ago so the bug can’t be there, the customer must be wrong?!
After running the application, waiting to not see the bug, it’s there again! You quickly head to your source code and… yikes, your old code is there, with no traces of your fixes. You compare it against other versions and can’t find a git change associated with your name. Was it a merge conflict or uncommitted? Could it have been the Matrix conspiring against you or even gremlins?
Keep reading this post in the Mobile Jazz Blog