Wisdom makes employee-reported bugs easier to reproduce

Transcript

Transcribed by machine (Whisper) from the episode’s audio, so a word may be off here and there.

1. 1:17:55

   So that class of PRs can be onboarded to this automated manage loop. This is nice. I like it. And then finally, I heard about wisdom. What is wisdom? Oh, yeah. So we use wisdom because all of our employees dog fooder products. So if you're using a rider app or earner app, and if you see any bug, then you can, from the app, report that bug. we now have all kinds of ai stuff where like it will automatically route it to the right team based on the stuff and then when you report a bug because it's from the employee from the employee like beta apps we can capture a whole bunch of logs and telemetry around that that makes it really easy for the team owning that feature to fix it so like in this case it's like an internal feature it's essentially like if you want to test any feature in a different country you can mock the

2. 1:18:51

   location on the device so if someone reported um that that that issue the first thing is okay now how do you reproduce that before it is it used to be a huge problem to reproduce so now we know that the set of screens the user has gone through because we have that in the logs and then we can give the engineers like this is the reproduction steps and this is the expected behavior and this is the observed behavior and so that we can boil down to the issue quickly and all of the telemetry that we collected from the app you can see all the logs in one place so like whether it's analytics network requests all kinds of feature flags so that also gives a lot of context and now now that we have all of this context we built a managed agent called debug assist that looks all of this looks at the code base and it will try to pinpoint what is the root

3. 1:19:43

   cause and like what is the impact evidence timeline around that um now i once i think okay this is the right right root cause i can hand off this to minion that we talked about yeah hey like this looks good like why don't you create a pr for this minion will take all of that context that we have it creates a pr it will attach that pr to the jira task the jira task also has the root cause analysis so anyone who's working they know the root cause analysis if someone updated the root cause on the comments or like create a new pr again all of that is data that we can then figure out okay how do we improve the debug assist how do we improve minion we didn't get the right rca or we didn't get the right pr from the rca like both we'll be able to continuously improve and then so do i understand correctly that you can capture and reproduce bugs so much easier right yeah and

4. 1:20:36

   we also added ability to because we for the employee reported bugs we have all the logs i can taste take my test device and i ask i can ask it to simulate what that employee has experienced so then i once i give the bug uid we can essentially serve the same network uh responses that we served to the person who filed so that i can experience the same issue in my test device app too. So that way, okay, then once you fix it, then I can see, okay, this actually got fixed. And then it makes it really easy to reproduce.

5. 1:21:13

   I love the recording of the thing because that's I mean, so important, right? Like it's hard enough to do even on the web, you need to build custom tools for yourself if you want to do a website. But it's awesome that you did it. Yeah, I think this helps a lot like then in reproducibility and like getting to the right root cause. So you built all of these systems and especially last year it seems so many brand new systems that are just doing