Transcript

[sid]: Hi guys. Hey Sid, what’s going on? Yeah, going good. [Michael Houck]: Had a good weekend. How are you? Nice. A little chaotic weekend, but it happens sometimes. UNKNOWN_SPEAKER: Hey guys. [Rafael Bruno]: Hey Rafael. Let me just move here because my wife doesn’t like to be on camera. [Michael Houck]: All right, guys, I wanna just dive into it. I have some stuff going on at home, so I’m probably gonna need to jump soon, so just want to dive right in. Let me share my screen. UNKNOWN_SPEAKER: Where is linear? [Michael Houck]: Does not show up. UNKNOWN_SPEAKER: Why does it not show up? [Michael Houck]: Oh, there it is, okay. So let’s see. Let’s print. We completed an OK amount of stuff. I would say there’s some stuff I was hoping to get across the line that we didn’t. But you know, we made some progress on things. But that means that this sprint has more stuff in it than I thought it was going to come in to finish those those things. The big one that came up last week was the issue that Rafael and Rizwan have been digging into around why broadcasts were being marked, why engagements were being marked as late or missed when they weren’t. We’ve identified what’s going on and we’re addressing it. Rizwan posted an update in the channel about that. We’ll see throughout this week how that kind of progresses, but it’s obviously an existential issue. So we need a solution. So they’re on it. I feel good about that. Direction we’re taking. UNKNOWN_SPEAKER: Let’s see. [Michael Houck]: Any other thing urgent that I want to call out? No, I don’t think so. Sid, let’s start with you. [sid]: Where are we at on groups? On the group side, we are testing it locally. I think Rafael has to do some fix for the referral thing. But in the meantime, I and Mehul were testing the inner circle flow starting from the sign up to including invite and including sending broadcast and everything. So we are just waiting for the last fix from Rafael. Once that is done, we will do another round of testing on dev. And that’s when even like we will inform you as well. And then if like all of us there can test and after that, we can prepare for launch depending on like, what, what, like how the feature looks like, Okay, cool. [Michael Houck]: Do we think we’re going to be able to launch this week? [sid]: This week? Yeah, sure. Sure. We are on track for that. It’s just that we need to test end to end on the dev environment on local, we are sure that it’s working properly. But like testing on a dev environment gives some some satisfaction. So once we are there, we’ll get a better clarity. But I’m pretty I’m not sure. UNKNOWN_SPEAKER: I’m not sure. [sid]: I’m not sure. [Michael Houck]: I’m not sure. I’m not sure. Hopefully we can get through these pretty quickly. They’re not. They’re not huge tasks as far as I can tell. Let me know if I’m wrong about that, but as I mentioned in Slack after that you’re going to be moving on to content queue. So for anybody who hasn’t read that content queue is a new service or new offer within the dashboard where users are able to request us to write pieces of content. For them on a one-off basis. And it flags it to our writing team in Slack. And then we deliver the content to them within a couple days. So, pretty cool offer. Because increasing the content quality is a big way that people can stick around on the platform. Because they do better performance-wise. So, we need to make sure that everything is represented in these tasks. So, Sid, I don’t know if this is everything. But please feel free to add everything. And then we’ll please do the same for the front end, even though it’s not your top priority in terms of what to work on next. I think that having the tasks in here ahead of time will be helpful for me. [sid]: So please take care of that ASAP. Yeah, sure. We’ll do it. [Michael Houck]: I’m just waiting for the inner circle to wrap up, but I’ll do it soon. Cool. Thank you. Um, okay. And then, um, where are we at with your stuff right now? [Mehul Jariwala]: I guess I was jumping between the groups. Project. So, myself and Rafael, we are both connected and we were testing the few things on the referrer flow. Seems to be okay, it’s working. We found some minor issue, which Rafael will be going to take care from the API backend side. Frontend side, everything seems to be good. So, the referrer project is all good. Come to the group, I did all the integration. The only thing is like we need to test a different scenario. What happened when user has a free tier user, normal user, basic user and the pricing flow. So those are the thing which I was keep on testing to make sure like if I found something, I was fixing it parallelly of it. But in terms of integration with the API, all done. We just need to test end to end very thoroughly so that it can work functionally. After that, if I feel everything is good, I guess I was not kind of block on the feather one because I need your help on that. I did try to set up a few things, but it requires some of the plugging. So that is a third project which I was jumbling between. And after that, probably I’ll take a look at on the camping one. Cool. [Michael Houck]: Yeah, I know I’m blocking you on the feather stuff right now. I think that their login is finally working for me. So I’ll be able to buy that today. So you can be there. One question is on this one, 1070. Have you moved the DNS to Cloudflare yet? Or is that still something we haven’t done? No, no, not yet. [Mehul Jariwala]: We have to first take a look at the feather stuff. And then before moving this, we need to figure it out there. And then if it thinks like we need it, So we can move it there. UNKNOWN_SPEAKER: Okay. [Michael Houck]: I think that when, when we do that, when we move it to cloud flare, we should do it, um, like late at night, my time, uh, because it’s one of those things that it might take the site down for a couple of minutes or something. And so I just don’t want to disrupt people during their day. So we can plan a time to, to make that transition when it’s, when it’s ready. UNKNOWN_SPEAKER: Yeah, sure. [Mehul Jariwala]: I will let you know when, when I, when I will do it, probably we can pass take the feather one and then we can work on that. UNKNOWN_SPEAKER: Sweet. [Michael Houck]: And then on the campaign side, obviously there’s more tasks in here too. All the things in here right now are frontend. We haven’t added the backend tasks yet. Rafael is going to do that maybe this week, hopefully. Excuse me. But if you feel there are any others that you can fit in this sprint, I don’t know if these sizes are correct. I just estimated. So feel free to pull them in as well. Probably the big first three. So that’s why I included them. [Mehul Jariwala]: Okay. Just one question. Uh, are we not doing the account self project? Uh, I will prioritizing the camping first and then a concert later. [Michael Houck]: Yeah, exactly. We’re still doing account shelf. Uh, just unless it’s blocking something that I’m forgetting, then let’s do campaigns first. [Mehul Jariwala]: Okay, cool. Makes sense. UNKNOWN_SPEAKER: Yeah. [Michael Houck]: Thank you. Um, what about you? [Rafael Bruno]: Okay, so today I checked some stuff regarding the issue with the scraper. I also tested the two flows with Mehul. The free tier flow, everything is working. What needs to be fixed was already fixed. And the referrals flow. About the referrals flow, there is only one thing that I need to fix here. That is related about creating commissions to the referrers. So after I solve this, I’ll let you know how so you can test end to end and make sure everything is working. Okay, great. [Michael Houck]: When I’m looking at my calendar for the week, I will have a lot of time tomorrow and on Wednesday and also part of the time on Thursday to do testing. So just keep me in the loop when when things are ready on both projects, both referrals and groups, and everything that’s sort of related to this release, and I can spend some time with one of you guys on a [Rafael Bruno]: call to go through everything. [Michael Houck]: And I guess, yeah, the big thing, Rafael, is just the scraper. Just please communicate overly with me this week. Just keep me in the loop on where we’re at, because it’s on my mind, it’s high priority, and as I mentioned, some stuff outside of work going on that’s kind of taking up my time. So it’s hard for me to remember to reach out to you guys. [Rafael Bruno]: So please proactively reach out to me. UNKNOWN_SPEAKER: Okay. [Michael Houck]: I’ll do that. Cool. Okay. I think that’s everything. I’m going to jump off. If you guys have more stuff, feel free. Ben, anything urgent on the customer side that we should flag before I jump? Or is it just the same issues we’ve been dealing with or unrelated things? [Ben Ornstein]: Pretty much the same stuff. Stuff, mostly onboarding issues, 12, 12, two weeks ago versus 11 closed conversations last week, about the same. It’s usually one-off people trying to reschedule or reopen their accounts on some lingering onboarding issues, but nothing like absolutely major. I mean, the onboarding issues are, you know, important for sure. But yeah, other than that, it’s, it’s just creators. They keep reaching out about, their dashboards, but we already know about that. So well, okay. [Michael Houck]: Just keep flagging instances where those dashboard issues show up. I know they’re not new issues, but just, uh, it’s important right now that we know when it’s happening, if it’s still happening and what cases it’s happening and things like that. [Ben Ornstein]: Got it. It’s usually people who have already reached out, but just following up. [Michael Houck]: So yeah, just keep, just keep flagging it. Just keep flagging it. Okay. Yep. We’ll do cool. Okay. Thanks guys. [Rafael Bruno]: I will, uh, I’ll see you soon. So guys, anything on the technical side? [Ben Ornstein]: One thing I would ask, would it be helpful for me to do any testing on dev with like for end-to-end flows, mostly on the front end? [Rafael Bruno]: Because like those are the things I could probably identify. Yeah, that would be helpful when we finish the building stuff. If you could like test everything since they’re onboarding to the like sharing posts, it will be helpful for us to identify what might throw any errors or any UX problems. OK. Yeah, let me know. [Ben Ornstein]: And I can’t promise I can do it every time. No, I got mute. Am I back? No, you were there the whole time. Oh, now you’re muted. [Rafael Bruno]: Oh, now I can hear. [Ben Ornstein]: There you go. Okay, that sounds good. I can probably fit in some, some of that at some point. So just let me know when it would be a good time to test, especially with how, you know, having stuff going on, I can, I can slot in there. So yeah, let me know. And then I’ll, I can go through certain things. Most again, front end stuff I can probably, I’d probably be most helpful with. UNKNOWN_SPEAKER: Okay. [Rafael Bruno]: I’ll let you know. Sounds good. [Ben Ornstein]: All right. [Rafael Bruno]: I’m going to head out to you guys soon. Sid, Mehul, anything on your side? UNKNOWN_SPEAKER: Just one thing for my side. [Mehul Jariwala]: So we will keep on getting everyday mail regarding the Sanity IO. I’m not sure whether we are really, really using Sanity as a part of our application or because sometimes I haven’t get a chance to take look at when we got some error and get like involved into such like the found error as a part of the sanity because I’m just wanted to check are we really using sanity io for our error debugging. Are you using sanity? What is that? What package is that? [sid]: That there is a seed set up with that error. [Rafael Bruno]: Oh, sentry, sentry. Yeah. We are using that. I saw that Sentry captured a lot of errors, but since I was doing other stuff like priority stuff, I didn’t have time to fix those errors, but they are on my list and I intend to fix them over time. I need to spare some time on my schedule to work on those errors. [sid]: Mehul, give me some time. This in a circle that the group thing is launched, those errors will also be fixed. It’s just that we need to add some more token in our environment file. But because of the priority, later also, if that’s okay for you. [Mehul Jariwala]: No, my question would be like, are we that really helpful? [sid]: Yes, I have sent one, I can see issues. And I’m pretty much sure that even when like once we launch a group, it will be helpful to track where the errors are coming from [Rafael Bruno]: Yeah, the ideal would be like, we fix all of those errors. And we will be on a stage where we will have like zero errors on a day. If one error happens, we will see that and we will quickly fix. The problem that we have right now is that we have a lot of fears and we need to decrease that backlog so the platform can be in a better quality. [Mehul Jariwala]: But overall, yes, Mayur it is helpful. No, because I haven’t tried to integrate with the frontend yet with the major analytics. So I thought maybe I can get your thoughts on backend part. Then I’ll spend some time to take a look at how we can integrate it with the front end. [sid]: On the back end side, we are just using a global like we are catching errors in the global class. So that’s why it is helpful. We don’t have to update it each and every API. On the front end, you can have a root wrapper and the root component and then you can catch all the all the errors there. Sentry exposes a method called capture global exception. Like if you import all from Sentry and then do Sentry dot capture global exception, it will catch all the errors and report it to that Sentry dashboard. And there we can see what errors it’s showing up. UNKNOWN_SPEAKER: Yeah, sure. [Mehul Jariwala]: I’ll take a look at no problem. Thank you. [Rafael Bruno]: Yeah, that’s all the questions I have. UNKNOWN_SPEAKER: Anything on your side, Sid? [sid]: Yeah, all good. UNKNOWN_SPEAKER: OK. [Rafael Bruno]: See you guys. Take care. Mehul, could you please push all of the changes into dev so I can test it. [Mehul Jariwala]: Yeah, I have already posted if you just take a poll. Maybe you can make changes. [Rafael Bruno]: Okay, I’ll check that. UNKNOWN_SPEAKER: Thank you. [Mehul Jariwala]: See you.