Used to be the case for me too. A tough customer bug would take me days, sometimes weeks to resolve it. Please note - I am talking about the **tough P0s** here, not the ones which I could shrug off with a small config change or close the ticket with an exception handler code or minor logic change.
For those nagging ones, you know what I am talking about, I would endlessly
This story may sound familiar to developers who get P0 issues assigned. I have been in office over weekends trying to solve for that one evasive bug that occurs only in customer environment, for a critical customer who is sitting a thousands of nautical miles away from me and with me the whole dev team is in office, trying to understand the issue, search through some petabytes of logs in the system, and find errors in our error monitoring tool. All this while my partner is fuming back at home for another weekend spent in office.
So how do you think I would have reacted?
And I so wish Docker could solve it all 😇. But life ain’t that simple.
Which bugs are usually the tough ones which developers, customer support teams struggle with? These are the ones where there is a lot of guess work.
To summarise Tough P0 bugs are the ones you are absolutely clueless about.
Let us dig a little deeper here and run through a few examples of why P0 bugs are logged.
Some of the actions developers resort while debugging the issues.
Here is an example break up for you (not statistical data - just from one of those really frustrating bugs in the life of a developer):
And you know how much can it cost you in terms of Dev money? Okay I probably don’t need to tell you that 🙂
The bigger thing being all this time your customer is waiting for you to fix the issue?
Even bigger, you don’t know how many other customers may be facing the same issue.
This is how. What if we say we build the complete customer bug picture for you? Yeah - Xray of bugs or even better an MRI of bugs? It gives you a complete picture for you to help diagnose the issue - and that too in minutes.
With Zipy you can now eliminate all of the below steps:
Time Saving: 7 hours
Time Saving: 2 hours
Time Saving: 2 hours
So here is the takeaway, there won’t be a single developer out there who hasn’t handled a tough customer issue. Some of us have stories to share about customer bugs that gave us nightmares.
So you know the pain. There is a way out when you have the complete picture of who faced the issue, how it really happened and where in your code things are going wrong. Isn’t it almost heavenly, when you don’t have to ever go back to the customers to reproduce issues and when you can simply replay the issue in the form of a video. Best of all instead of spending weekends firefighting, you can sit back and relax and get to those nagging critical issues in minutes.
With session replay, logs, stacktrace, network traces, user identification, customer identification, advanced search, and surge alerts all built in one single tool, you don’t have to worry about reproducing customer issues anymore. You get to the root cause of any customer reported (and not reported ones as well) with Zipy in a jiffy. Why don’t you try it out yourself?
Feel free to comment or write to us in case you have any further questions at email@example.com. We would be happy to help you. In case you want to explore Zipy for your app, you can sign up here or book a demo here.
It is no less than a nightmare when a feature request from the product team is not getting fit with the current system. So this feature request required some heavy aggregated functions which did not give satisfactory results with a row-based database.
As a developer myself, the most complicated part of the job is not writing the code but reproducing an issue the customer reported, debugging, and fixing the issue. With such little information at your disposal, it becomes a nightmare to start debugging the issue, let alone fixing it. Can we do something better here?
Continuous Integration and Continuous Delivery (CICD) are terms used to describe a process where multiple changes are made to a codebase simultaneously. In very simple words, CI is a modern tool for development practice in which code changes are made frequently.