- Duration: 40 min
- Platform: zoom
- Source: Read.ai 01J53XKBRG60PHCTHBF0HN3FNA (https://app.read.ai/analytics/meetings/01J53XKBRG60PHCTHBF0HN3FNA)
Transcript
[Michael Houck]: Hey guys, what’s going on? [Sid]: Yeah, going good. [MJ]: going on like mega fun v2 going on. [Michael Houck]: Yeah. Lots of stuff going on big week. Um, okay. We got a lot to go over. Uh, we’re still waiting on out of bio, but I think let’s just dive in. Um, so I am feeling a little stressed about where we’re at and I’m sure you guys are feeling the same way. Um, Our original timeline, well, original timeline was for three weeks ago, but our updated timeline was to have the database out tomorrow. Seems unlikely that that is going to happen unless you guys tell me otherwise. So on this call, we need to identify what the new timeline is and do everything we can to make that as quick as possible since Rafael is going out after the end of this week for two weeks. And there’s no scenario where I’m accepting an idea where we push the database back. Our users will continue to revolt. They’ve already been sort of expecting this timeline. So yeah, I guess I’ll just turn it over to you to start, Rafael. Where are we at? What’s left to do? Catch me up. [Rafael Bruno]: Okay, so I’m still testing stuff. As I was sharing with Sid and Miho, we have some stuff on the database to arrange, but the code part is like done. [Rafael Bruno]: What I was talking with Sid is that since there is a lot of things to test yet, and I will be traveling on Friday, I I feel that if we launch stuff right now, it will be like hurrying stuff. [Rafael Bruno]: We still need to test and make sure that we’ll not deliver something that will have a lot of bugs or that will give a bad impression to users. So my confidence of releasing stuff now, it’s a bit low. [Michael Houck]: So your confidence in releasing it all this week is low, which means your confidence in the next three weeks is low. [Michael Houck]: It’s not acceptable, man. It’s not. We need to get this out this week. We’ve pushed this back. It’s been a two to three month project already. I know it’s a big project. I thought we were gonna be working more through the weekend. So we need to get this out this week. And I’m really gonna ask you guys to push so that we can do it. We take next week and then be a little easy as long as we get get it out this week. So yeah, I think what what do we need to do in order to get out this week. [Rafael Bruno]: fully test everything and make sure that there is no bugs or that we will not have a bad user experience. Because this is the part that I’m still not sure that we will have the result that we expect because we expect to deliver something that will not be fast, not only be fast, but that users will see a huge improvement without bugs and without anything bad. So I’m just a little not sure that if we hurry stuff, we’ll be able to deliver stuff without bugs. [Michael Houck]: Yeah, but it’s not hurrying at this point, right? It’d be hurrying if we were doing this three weeks ago. Now it’s not hurrying. Now it’s the fact is we’re behind schedule. So we should have been hurrying earlier is my point, basically. [Michael Houck]: So, okay. So to get it out this week, there’s three things we need to do, it sounds like, One is testing for bugs. Two is finish the integration with the scraper. And three is, integrate with the new onboarding flow. And my understanding is that the onboarding stuff, there’s not that much to do. The scraper, I would want to ask Sid sort of where we’re at with that. And then the main task will be, will be just testing, right? Yeah. Is there any other work that needs to be done aside from those three buckets? [Rafael Bruno]: Maybe there is one stuff that it’s not done because on Airtable, when we get the URL of the photo, we can start that directly on Airtable. But now we have to set up an S3 bucket to start the photos of the accounts there. But this is not like super complicated. It just will take like four hours to do. [Sid]: Yeah, I thought about this. So do you have a URL? Do you have a URL of editable which we can use? I mean, I tried opening some links from editable for the photo. And it’s it gives me the URL is not valid. And it like it basically gives me error. So do if you have a valid URL, I can populate in the database without writing any any extra code. But the only thing The URLs I have, I got from editable, they are all like not working. [Rafael Bruno]: I’ll check that. [UNKNOWN_SPEAKER]: Yeah. [Sid]: So if you give me a valid URL, I like it’s on me to populate in the database. I have already thought about it. [Michael Houck]: Okay. Okay. Sid, I’m going to create a small ticket and assign that to you. Um, mega eight 51. Um, yeah. [Sid]: Good. Sorry. [Sid]: Yeah. Yeah. Okay. [Michael Houck]: Okay. And then do you want to talk about where we’re at with the scraper? It looks like there are some things in review, but you had mentioned that one of the things there was one had set up, I think it’s mega eight 11 wasn’t returning something that you needed. Do we want to talk about that? [Sid]: Yeah, so I checked about it. And I mean, 811 is, I mean, it does give us what we want. I’ll leave a comment or I’ll just move it to done. So that is sorted. Then there are the few tickets in progress. Same goes for that also. I checked it. That we have it implemented. The only thing is that we have to test. That will be before the launch. I mean, I’ll test it on local before the launch. So I’m just keeping in progress until then. But at the development side, we are done with it. [Michael Houck]: Okay. So all the ones in review right now that are part of that Scraper project, we can move them to done. They’re all done? [Sid]: Correct. Yeah, they are done. [Michael Houck]: Okay, great. I’m going to move them to done right now. [Sid]: We can move to InReview and test it once we are about to launch. [Michael Houck]: Great. [Michael Houck]: OK. So then, Mahul, on the onboarding side, what is left to do there? I know you’re working on that. [MJ]: So I have already finished the Create Account flow. It was working fine. I’ve integrated with the new API, able to redirect to the contact info. Probably I will finish the contract for today as well. And then we have the ad account. That is also not a big deal. That can be done tomorrow as well. I will finish everything. The only thing which I am worried about is the scaper. Are we going to show the scaper screen? [MJ]: two or three based on that. We will show showing those screen. So that is thing. I’m only worried on the pricing page. So pricing page, I guess, uh, the existing scenario on the right, there will be no changes. And, uh, as we discussed last time, we just need to remove the free tire and we update the plan a bit. [Michael Houck]: Yeah. You can go back in the team channel, the message I sent on Friday that has all the details of the little minor changes we need to make there. I know you’re on top of that. As far as the scraper, Yeah, these are the what is this? This is 712 and 711. Sid, are you able to get these done? I guess it’s like your next your next thing here. [Sid]: Yeah, I mean, I’m currently working on the dashboard thing. So I’m writing code, but again, I have to test it. And that is partly related with the launch. I mean, getting the APIs to work. So I’m already in talks with Rafael. Once I, yeah, like once I’m able to test the dashboard APIs and once this is done, I’ll pick up 7.11 Okay. [Michael Houck]: When do you think that will be? [Sid]: So writing, I mean, coding is 50% done, 50% remaining but testing is difficult. I’m still getting some database related errors, which I shared with Rafael yesterday and today also. But I mean, I’ll connect with him again after this stand up, which I’ve already shared with I’ll connect with him and get those sorted. I mean, if it is something that he needs to do, then it, I mean, he will fix and then let me know if it is something on my side, which we have to figure out. I don’t think it’s an issue on my side. I mean, all the APIs are not working for me, but I’ll have to check with Rafael. [UNKNOWN_SPEAKER]: Okay. [Michael Houck]: So there’s work on the APIs we need you to get them fixed. [Michael Houck]: Yeah. [UNKNOWN_SPEAKER]: Okay. [Michael Houck]: Okay, and then we have the S3 storage. That sounds like it’s not that big of a task. [Michael Houck]: Yeah, it does. [Michael Houck]: Okay. Okay, cool. Yeah, and then I see you have the dashboard thing. What is that? 793 the one you’re working on right now. [UNKNOWN_SPEAKER]: Okay. [Michael Houck]: Cool. Um, Rizwan, how about on your side, anything, uh, blocking, um, launch or how are we doing? I know we’ve been going back and forth with the account defy guy. [Rizwan Hameed]: yeah so we i’ve just received the new accounts as well just like you saw also at the slack channel so the three bots for the post engagement confirmation are already deployed and working and like you know they are able to accept the events just one thing on a field I’m not not getting the check for a key in the events still. I tested it but the key is not available over there. So the events are not being processed based on those keys. So these three post engagement confirmation instances for the Twitter are running and now I have started the machines for the LinkedIn one as well. And I’m just, you know, setting up the LinkedIn accounts on those. So the code related changes are done for the confirmation and once the accounts are integrated, I will let you know right away. And after that, so engagement confirmation will be fully in functional to proceed with the different types of events like, you know, five minutes events, one hour events and 24 hours events as well. [Michael Houck]: Great, that’s really good news. Great work on getting that on the timeline that we needed. I know it was a lot of work. I appreciate it. [Rizwan Hameed]: I guess just to tune down the excitement. So it’s like, you know, this is a manual scalability, right? Just like I mentioned, this is a manual scalability. Like, you know, I’m manually creating the machines, setting up the accounts. In the future, definitely after this release, definitely I will suggest a plan for the auto-scalability. [Michael Houck]: Right, but we don’t need that right now. That’s not a blocker right now because it’s not like we’re going to go to 10,000 users tomorrow, you know, so it’s fine that way for now. [UNKNOWN_SPEAKER]: Okay. [Michael Houck]: Are there any other of the bots that we need to have set up on LinkedIn, like the profile photo one or the follower growth tracking one or all those kind of set up too? [Rizwan Hameed]: Yeah. So those were set up, but there was an issue with the account that were, that was being used. So that’s where I stopped it. And after that followers on boarding bought, that is our remaining one, which I need to deploy. [Michael Houck]: Okay, cool. Um, once, uh, I guess once you get the accounts integrated, uh, then you can move on and, and keep working on those and get those across the finish line, um, as needed to. [Michael Houck]: Sure thing. [Michael Houck]: Cool. Autobio, how about on your side? I know it sounded like you made some improvement on the tone adaptation last week. [Adebayo]: Yes, I made some improvements on the tone adaptation, but still nowhere at the place I feel like we can bring in human annotators to start looking at it. So I’m continuing to work on it this week. And my aim is that by Thursday, should be ready for the team to review. So that we get the first round of feedback and then we can iterate from there. [Michael Houck]: Cool, sounds good. And the latency, is that still ongoing too, the latency improvements? [Adebayo]: Yeah, because part of the reason I’m working on them side by side is because part of it is changing prompts. So if the prompt is longer, it means that the latency will be longer and all of that. So I’m working on that side by side. And by the time we get to a place where we feel like the quality is good, then we can now push on fully on bringing latency as much as possible. [Michael Houck]: Okay, got it. Do you think both of those will be wrapped up as part of this sprint this week? Yes. Yes. Okay. [UNKNOWN_SPEAKER]: Cool. [Adebayo]: I believe so. [Michael Houck]: Okay. So I think that what’s clear to me is that the big thing, the big blocker is the testing, Rafael. Am I right about that? That’s like the one thing that’s making us concerned. It sounds like everything else we’re in a pretty good place on, but we just, we need to feel good about the quality we’re putting out. So we want to do robust testing. Is that fair? [Rafael Bruno]: Yeah. [Michael Houck]: Okay, what can we do to ensure that we get that done quickly? [Rafael Bruno]: I think that I can divide part of the load of testing with seeds. That’s the only thing that I can think right now. [Michael Houck]: Okay, I think the issue with that is it said also has his own work that he’s doing at least I know so you give me a heads up of when these will be done, but right now it looks like there’s four extra small or small tickets, which would imply you probably won’t be freed up till like end of day Wednesday, maybe. [Sid]: Wednesday, Tuesday, Wednesday, about Thursday afternoon my time. So yeah, I mean, Thursday afternoon my time, I’ll be done with all those. If, if, I mean, while testing, if we don’t find any major bugs. For example, if they’re like small things, it’s fine. But if like many things are coming up during testing, then I’ll have to shift to that new box, which you find during testing and put these aside. [Michael Houck]: Got it. Okay. So it sounds like the chances of you getting into a place with this where you’d be able to help out on the other testing that Rafael is doing is going to be tough before like Thursday at the earliest. [Sid]: Yeah. Almost. I mean, a better time to estimate these would be after at least spending one day of testing. After one day, if we, if I and Rafael have not found many like bugs or any, like we have just found minor bugs, then it’s when we can address and then take over these. So that’s why I’m saying after one day of testing, we can say like, we can give, like, I can give an opinion when I can finish these or, or, or at least when I, when can I start these. [Michael Houck]: Okay. And then, Rafael, on your side, once you finish the testing, what if anything is left to do after that? [Rafael Bruno]: After that, just prepping stuff to release into production. One thing that I think we need to do before launching into production, it doesn’t need to be automated, but just make sure that we are making a backup of the database at least once a day. So we know that for some reason, if we lose or if it happens something, we know that we have a backup of the database. [Michael Houck]: Just that. Yeah, I mean, I don’t think that’s a blocker. [Rafael Bruno]: Yeah, no blocker. Just something to do before releasing. [Michael Houck]: Well, no, something to do before releasing would be a blocker, right? Because it blocks us from releasing. So my opinion is that’s not a blocker. It’s something we should do. Yeah, it’s a fast follow. It’s something we can do right afterwards. Because it’s not like anyone’s going to hack us the day that we launch the database, you know, like we’re fine. [Michael Houck]: Hopefully, fingers crossed, right? [Rafael Bruno]: Yeah, I’m like this because as I shared before, I had this experience of having the database that I was working locked by a hacker. So I know that those scenarios, although they seem like unlikely to happen, when they happen, it’s a bit of a headache to solve. [Michael Houck]: Yeah, I think if this was a couple weeks ago, I’d feel differently. Originally, we did want to get this in before releasing. But I think because of the the delays, uh, we just can’t do it. So I think let’s push this after launch. Maybe that’s something said you can work on while Rafael is, is out. I’m going to move this into, into next sprint. Um, Cool. Okay. So I’m, as I’m looking through this, um, Mahua, I’m going to move your group stuff into next sprint too. We can bring it back into this one if we get to it, but it’s not a, not a priority. Um, Prep for release. Uh, there’s one ticket that I’m not sure if we need to do it before we launch or not. It’s $4.99 getting events for inactive accounts. It’s a scraper task, but it’s assigned to Rafael. [UNKNOWN_SPEAKER]: Right. [Rafael Bruno]: Don’t remember that. Let me check here. [Rizwan Hameed]: Yeah. So it was like, you know, I was getting the events for the profiles, uh, or the accounts which were not active in the air table. [Rafael Bruno]: Oh, OK. [Rafael Bruno]: I think I remember this one. This is easy to do. It’s just like one or three lines of code that I have to add. So inactive accounts don’t trigger that. It’s easy to do. [Michael Houck]: Got it. OK. So if it’s extra small, then we can leave this in. If it’s literally just three lines of code, that’s fine. [Rizwan Hameed]: And one more thing. Mehul and Sid. They are testing the bot or giving a tough competition to the scrappers by putting the fake links. [UNKNOWN_SPEAKER]: What’s that? [Rizwan Hameed]: The fake links, the profile fake links. [Rizwan Hameed]: Testing links. [Rizwan Hameed]: They are giving a tough competition to the scrapper. [Michael Houck]: Yeah. All the test accounts and test posts and things like that. That makes sense. [Michael Houck]: That’s funny. Okay. I’m looking through everything. It sounds like the biggest thing is just testing. So I think, Rafael, we have to get this out this week. There’s no world where we can let this linger beyond this week. We have users who, they’re literally emailing me every day. Like two people are literally emailing me every day asking me when it’s gonna be fixed and threatening to turn. And every day I’m having to have a conversation with them. I’m like, no, please don’t turn. It’s coming this week or it’s coming soon. Yeah, I understand. Yeah, so we just can’t push it anymore. [Michael Houck]: Like, is there a way to either move through the testing faster or defer some of it and just deal with maybe smaller bugs? I don’t know. What are your thoughts there? [Rafael Bruno]: Yeah, I can focus on, the more important flows like creating a broadcast or making a payment, I can focus on those stuff first and then leave the rest later after the core of Megafone is solved. [Michael Houck]: Okay. If you do that, then would we be able to launch, I guess, on Thursday? [Rafael Bruno]: I’m not sure. I want to have all the core ready by Thursday, but I’m not sure how to give this estimative. Because how can I explain? The rule is ready, but I’m not really sure what kind of error I may find while testing. So I will work to make it ready. But I’m not really sure if I will be able to make everything ready. [Michael Houck]: Basically, what you’re saying is there’s a layer of uncertainty of like, I don’t know if these are going to be complicated bugs that we find or simple bugs. [UNKNOWN_SPEAKER]: Yeah. [Michael Houck]: Yeah. [Sid]: Okay, Rafael, have you tested like, well, while you’re doing the migration stuff have very able to test the API’s like, have you just translated the code without testing or in between? [Sid]: Sorry, could you repeat, please? [Sid]: So when you started with the migration stuff, right? Were you able to translate? Were you able to test the API’s one by one? When when you were doing that, or you were just updating the code without testing? [Rafael Bruno]: No, I was updating without testing. And this testing is the last phase. [Sid]: So I think testing will be difficult then. I mean, we have to test each and every API endpoint because, I mean, you left it to test at the end, but then it means we have to go back. [Sid]: Yeah, because there was no way to test before because I was adopting the schemas. Yeah, yeah, yeah. [Sid]: I fully understand with you. But I’m just saying that if it’s at the end, then we have to give more time to it and go through each and every API route. Anyways, we can split it and test. We can create a plan and test it. [Rafael Bruno]: OK. [Michael Houck]: OK. I think I know this is a big bunch of work here to do with the testing. Rafael, are you working Friday or do you leave? Like, are you gone on Friday? [Rafael Bruno]: No, I’ll be working. I’ll be working Friday. And possible. But I’m not sure. Possible like Saturday morning. But I’m not sure. [Michael Houck]: So then, OK, at the at the latest, the latest time we could launch is like Friday night, like overnight. Yes. [Michael Houck]: I would obviously prefer to launch sooner in the week so that we can debug if things come up. But if we’re going to do the testing at a time, we got to do the testing ahead of time. So, Sid, I guess anything that you can do to help Rafael out and lighten the load, please do it. Obviously, I know you have your own work here as well. And that stuff is part of this launch. So Yeah, I think you guys should huddle up and try to split up as much as possible so that we’re in best position to launch as early as possible with like a firm go live date being Friday night. Like we have to be ready by Friday night. And if we can’t be ready earlier, we should, because Friday night would suck to launch. But yeah, at the latest, that’s when we’ll do it. [Sid]: Yeah, sure. I’ll catch up with Rafael and create a plan. [Michael Houck]: OK. Cool. Sounds good. Let me in as needed. Um, and we’ll, we’ll talk on Slack. Okay. [Rafael Bruno]: Yeah, sure. [Rafael Bruno]: Uh, so guys, do you want to discuss anything? [MJ]: Just one thing, my side, so did you create it? The, the, that is one thing, right? Which we used to check the, I guess I remember that, uh, is, if I remember correctly, I pointed to the same thing in API. [MJ]: User is user that we used to call that API to check whether the user is already used to completed the signup rule or not. [Rafael Bruno]: And then if not, I answered that on another thread. The new endpoint is the It’s that one that I sent you the screenshot to check the user state based on the user state. Okay. Okay. [MJ]: So that is the replacement of that one, right? Okay, cool. Yeah, that makes sense. That’s that’s for my test. Okay. [Rafael Bruno]: Rizwan, I know what is causing you to not receive the check for in like half an hour, this will be on production. So you will receive that. OK? [Rizwan Hameed]: Sure. Thank you so much. [Rafael Bruno]: OK. [Rafael Bruno]: Anyone else? [Sid]: Rafael, can you stay back? Sure. [UNKNOWN_SPEAKER]: OK. [Rizwan Hameed]: Guys. See you. [Rizwan Hameed]: Bye. [Sid]: Hi Rafael. So like any clue, like how many, how are you feeling? Like, have you any, any clue to start with? [Rafael Bruno]: Yes. So as I said to Raul, I will focus on testing the main eight points first and let, let the others, let the others at the end. So the main endpoints are the ones that create a broadcast and the one that Make sure that the user, basically everything on the broadcast module and everything on the users module. Those are the main endpoints. I will focus on testing them now. And as I said to you, that was one of the reasons that I didn’t test before. In order to test, I needed to finish all the migrations of the code. And before testing, I need all the data on the database to be ready so I can know that I can query and get the response that I am expecting. That’s why I needed you to finish those migrations first on the users, casters, and amplifiers table before jumping into testing. [Sid]: Right. So I understand and therefore I did that. I finished as I mentioned. So maybe what I suggest is you can start, you can take a look and also let me know what I should be testing. So if you’re taking over the broadcast and the user modules, what parts of the system should I test? Is it payments? Is it the amplifier flow? Maybe can you elaborate? [Rafael Bruno]: I’ll let you know. Since you’ll be working on that, on the other stuff first, you have a lot of work. Let me just check a message that you sent me here. [Rafael Bruno]: You’re trying to get the broadcast of a caster. I’m not sure why this error is occurring. I have to check here. [Rafael Bruno]: Is this very important to you right now? No, no, no, OK, I will let me make, let me find something here first. [Rafael Bruno]: We have about 148 points. [Rafael Bruno]: of those know 140, that like of them are working, or they need just like a few things to finish. [Rafael Bruno]: I have one idea of why this is not working, but I have to debug it here. But if you want to start, like, wait a second, what is your priority right now? Because I know that you said said that you’ll be working until Thursday with something, right? [Sid]: No, no, no. So the priority is testing, OK? You are testing the broadcast and the user module. So what module should I be testing? [Rafael Bruno]: Oh, OK. So there is one stuff here. Oh, this is another stuff that we need to migrate. [Rafael Bruno]: Before we had like the transactions table and on the transactions we had deposits, we had subscriptions, payouts. Now we have, if I’m not mistaken, five different tables. We have, let me share here. [Sid]: We have wallets, we have deposits, subscription. [Rafael Bruno]: Yeah. [Rafael Bruno]: Wallets and there’s one more. [Rafael Bruno]: Can you see my screen? [Rafael Bruno]: Yeah. [Rafael Bruno]: So one thing that we don’t have right now on the table is the wallet table populated. So this is what I need from you. Each user should have a wallet. So we need to assign to create a wallet for each user. And we should put on that wallet entity the IDs of the accounts of the users, the total value of charges, total value of deposits, earnings, referral earnings, subscription payments, and withdrawals of that user. [Sid]: Okay. [Sid]: We have it populated. If you check the production database, I didn’t check that yet. [Rafael Bruno]: Let me check here. [Sid]: We have about 1600 records. [Rafael Bruno]: Oh, that’s really good. One thing that we need to change, we won’t have any negative values here. So here, charges and anything else, those should always be positive numbers. [Sid]: Okay. Okay. I can check. It must be because we have it that way in the editable, but I can double check and see why it is coming in negative. I’ll make sure if it is indeed in negative in editable, then what should the value be here? [Rafael Bruno]: It should be the same value, but positive. 0 No, no. For instance, this one here is minus 15. It should be 15. Here is minus 4. You just need to multiply by minus 1 to get the value. [Sid]: I’Ll check. Yeah, yeah. I’ll check. I got the point. I’ll check that. No worries. [Rafael Bruno]: OK. [Rafael Bruno]: Let me see one other thing here. [Rafael Bruno]: There’s no charges. [Sid]: Charges must be empty. I’ll have to populate that. [Rafael Bruno]: Let me see. We also need to populate that. [Rafael Bruno]: Subscriptions is. Also empty. I think those are also… [Sid]: Subscriptions is also empty. Wallet is filled up with the data. Maybe you can test that. Wallet is done and deposits is also done. [Rafael Bruno]: Okay. I’m testing here on the broad database, but deposits is also empty. [Sid]: Okay, so give me some time I’ll fill up all those tables deposits. I mean, I also want to test it. So I did not I have the query with me. It’s just a matter of minutes for me to run and fill the data. But I also need to verify so I haven’t done it. So I’ll do I’ll verify it first in that table and then I’ll populate. [Rafael Bruno]: Okay, so when you finish populating, let me know and I’ll let you know by which endpoints you should start checking, but it will be on the finance module. [Sid]: Yeah, sure. Sure. Got it. So for me, there’s a finance module and you I think you have all the data in the database for the broadcast and the user module, right? So that is that won’t be an issue. [Rafael Bruno]: I don’t have I’ll let you know so you can finish populating Sure. [Sid]: Sure. Sounds good. [Sid]: I think you should have it. It’s just those four tables which are missing. I mean, which I haven’t done it on purpose. We have the data in dev database, but not in production because I want to, I want to test it. [Rafael Bruno]: Oh, another thing. I think we should not test on the production database. We should test everything on the dev database, because from now on, we should not put test data on the database, on the production database. Do you understand? [Sid]: I get your point. [Rafael Bruno]: we should let the production database only to like, see if there is something wrong occurring on production. So what my main go ahead. [Sid]: Yeah, you have a point. What I’m thinking is, if we see why I used production data, okay. The thing is, all the all the correct data with all the correct columns or with all the latest columns, we have it in production database. Okay. I mean, whatever. [Rafael Bruno]: Can’t you just like make a, I’m not really sure how to do that, but to repopulate all the dev database with the production data. I can erase, erase the data dev database and create another one with the production database based on the, uh, the backup of the production database. [Rafael Bruno]: Um, I think this is the fastest way to, to solve that. [Sid]: Yeah. Good point. Good point. I’ll take care of that one. Give me some time. I’ll take care of that one. [Sid]: Uh, but until then you can test on production, right? [Rafael Bruno]: Okay, I’ll do that. [Sid]: Okay, cool. Makes sense. So continue. I’ll take care of that tomorrow by time and make sure that the production whatever we have in production is same in dev and staging. [Rafael Bruno]: Okay, I’ll keep testing here. And by my the end of my day, I’ll have everything set for you. So you can also test when you start to work tomorrow. [Sid]: Yeah, sure. Sure. Sounds good. [Sid]: OK. [Sid]: All right. [Rafael Bruno]: OK. Thank you, Sid. Have a good night. [Sid]: Yeah. Have a good day. Bye bye. See you. [Rafael Bruno]: See you.