Michael:
Hi, I’m Michael he’s up door. It is Friday, June 19. And we are back in it two weeks in a row you get in our weekly our weekly calls going here so this is good stuff. Our weekly update for bionic WP. That’s what we’re talking about today. Ah, some news actually happened this week in, in Karachi, Pakistan.We were able to open the office and we were absolutely crushing it had amazing progress. And then
Abdul:
we had to shut it down. So he like last week, he said we are opening the office. So in one week we opened and we closed a very impressive kind of feed and opening the office but the four days that we did get into in the office like they were amazing. And we did accomplish a lot. And I think they were good in a way that because we have a few way technical features that we’d be working on the team is working on. So they got four days to kind of work on that talk about that. Make sure that they all understand what they’re doing. But it’s not something we had planned for. We will have the view that now it’s open and we will be there in the office. But definitely having everyone safe is very much more important. So that’s what we the government decided that they have to impose a two weeks lockdown in selected parts of the city, which happened to be like 70% of the city. So we also all like most of the guys that were yes that they came from with our offices all got selected for that lockdown. So we did have to like we were there for four days from Monday to Thursday. Today, we all again work from home, but I think we did carry forward some of the momentum because like now that everyone knows each other more. They have worked together like they had pulled together. So you know that, that kind of at least he got that in the in four days. So I think for the two weeks that we were like working from home, we’ll be able to make, like, you know, they use some of that kind of momentum. But definitely like, it is a kind of everyone is kind of off by that because he was expecting to work from the office.
Michael:
Yeah, I mean, as you know, Abdul and I were talking about how to give me more engaged and how the and then all of a sudden, it fell apart, right, just like that. So, you know, hopefully it’s just for two weeks. That’s what we’re hoping for. So I think June or July what they did, I think in a second. So it’s really I mean, I guess it is two weeks but
yeah, so we’ll we’ll we’ll play the hand we’ve been dealt and we’ll move forward with that. I think you like you said we had a ton of great progress. We saw some cool things we camps and new nicknames for a couple guys because they’re just been some stuff so one guy’s his nickname is API. So it’s it’s kind of fun to see that happening guys building some camaraderie together and being able to hang out a little bit is is kind of fun. And based on that one building
Abdul:
that because they all came to office, they work really hard on that. They all showed us like their capabilities as well now. So now the thing is like today like when we were having a standard, we were like, okay, we were expecting a little more on this side, right? So the thing is, because now we know like everyone we understand, like working from home, not all of these guys are, like experienced in that like in there like, it becomes a little difficult for people who don’t have that kind of like an environment where they can work in at home, but still like so now we at least know how much API’s that API gate can build in a day, stuff like that. So I think that just gives us more kind of leverage as well.
Michael:
Yeah, and I think we’re also implementing a pretty strong QA process right. We have a new quality Insurance person. And I think today in our company meeting you mentioned he’s kind of kind of like the police, right? Like he’s, he’s pretty strict. He’s been re rejecting tickets, knocking them out of the air and putting them back on the developers to get that work done again. And it’s cool to see somebody stepped in right away and not be afraid to do that by like ruffling people’s feathers or, or doing whatever, but he came in and is doing his job exactly how he wants to. And he’s in our daily stand ups with me now providing feedback and what we’re seeing you
Abdul:
want to kind of expand anything on that. I think that is the first thing that I kind of made sure, because QA definitely is like a very, very important part of the whole, especially if you have a product and you’re working on a product. So it’s very important because you know, like there are so many moving parts. Developers work different developers working on different things, their chances and then with the timelines that we have, you’re pushing code really fast. So there is a need for having a very strong process to make sure that at least we can avoid the errors that we can make because something’s you only comfortable when they’re in production, when many people use it, but at least the small stuff that we can catch early on. And that’s the reason we had one guy who joined in today or this week on Monday. And then last week, so and then we have another QA guy, a more senior guy joining from Monday. Right, so we have two QA guys, that will be there, like the one that’s joining on Monday, even more experienced, right? So I’m expecting that we will have even more kind of rules on in place for that because I think and that’s it was very important that I like when I had first discussion with the method, okay. Like from our side, from the management side, no one will ask you like, I will never ask you why the ticket got rejected. It’s your that you have full authority when it comes to you the guy because if everything anything goes wrong, I’ll be asking you. And I won’t ask the developer as a developer. Second, I’ll ask first, like, how did it get through? So I think that’s also very important to make sure that the QA that everyone knows they can I was I’m very happy that our lead developers on board on that as well. And he has similar instructions to the QA guy to make sure that everything that goes to eclipse follows all the fop that we have set out, and things like that. Because right now we are we are we are code base is growing very fast. And, and I expect that by in the next 12 months, if once we like 12 months out, our code base would be really large and really complicated. So, it’s where it’s best to stablish good practices right away, right, like from now because, like, you know, like, technical debt can be like, it’s, the more you talk, the more you’re willing to pay, the more the more interest you have to pay on it.
Michael:
Yeah, so we have those two QA people, one of them starting Monday, then we have three other people starting Monday, why don’t you talk about those three other people that we have coming on board? Yeah,
Abdul:
so our team is growing quite rapidly. So we have 234 minutes to
Michael:
slow down a little in a couple
Abdul:
Yeah, beyond make almost at the end of or you can say, this quarters hiring and even like next quarters hiring, we might like next we might be
Michael:
adding some support. Well, yeah, so
Abdul:
the only position that I think will be there, but but we almost at the end, we just are looking for maybe one or two more guys right now. But after that it’s, it’s done. So the four new people that are joining in on Monday, one of them, like I said, it’s the QA guy. And then we have one designer joining in to help us with all the design parts of the platform and
Michael:
other things, that person will have their hands full, that’s for sure they have a lots of things to design,
Abdul:
a lot of things and a lot of people waiting for him actually to join because like, that’s a lot of the I think a lot of things out there, but it’s good that he has a lot of work already there for him to start. And then we have two DevOps engineers joining in. So and this was a non key position that we were looking for and looking for the right people to join. So we have to do Guys to ending in one of them would be more towards the DevOps development side where development scripts and stuff like that. And the other guy that’s joining is more toward infection monitoring. So he will be kind of the infrastructure support guy making sure all the servers are working properly and stuff like that. And then we also have one guy joining from the from next Monday from pretty nice, that’s a support person, a WordPress engineer.
Michael:
And we’re very excited about him as well. So and then lastly, kind of the last thing for the week we update is, you know, it’s kind of funny, we got into the office and everybody was, uh, you know, working together. So we saw how efficient everyone was. So we added some more things to the task list that they needed to do. I’m going to presentation in Miami, middle of my or sorry, middle of July and end of July given two different presentations in Miami. And we want to have some sort of platform ready to test and show People have a this is the speeds your current sites at this is what your speed can be in with our platform. And I think it’s going to be a great sales tool. So we’re trying to get that built now as well. On top of obviously building the normal platform I’m sure a front of Hassan love when you and I sit together and brainstorm new ideas of things we can build. So that’s kind of interesting.
Abdul:
They are now kind of told me that they from next month onwards, they won’t be accepting the feature list on its face value. They only told me that that they will be not accepting it just like okay, they feel Yeah, that it’s a good feature list. They will be like kind of will be go and I think that’s the process that we wanted to develop, like each feature discussed pre beforehand. So like they know exactly what they are. So when they commit to something they know exactly what they’re committing to. And we can also be sure okay, like this is well understood kind of a product and like a feature and we everyone understands what needs to be done. We accomplish that we tricked we tricked him once that’s
Michael:
for sure no, not let us do that again. But it You know, I hope I hope you and I will, you know, dial it in as we go. But I mean, this is part of who we are and what we do, we see things that we need. And the team needs to be able to shift a little bit, obviously, you got to keep our eye on the prize, and get that completed. But we still have to be a little bit nimble in developing things to support the tool to help close deals and whatnot.
Abdul:
And I just so added on that point on being the nimble part. That’s one of the reasons that we have followed a very API focused approach, because I think we haven’t had a chance to discuss like, what tech stack we’re using and stuff like that. And that’s one of the reason that we chose lumen, which is a micro framework from Laravel. Right? Laravel is a very big PHP framework. So we using lumen because the idea was that may not be the whole back end that we are building. Like, it’s nothing but API’s. And that’s why like, you hear a lot of API discussion going on, because like when people expect, okay, they’re back and there’s something happening is all API’s for us like every function Every button that’s there on the front end is povery is being powered by an API call somewhere. So it’s a very API, there’s a very minimalistic kind of a back end, just an API. That’s working in API favor. That’s just responding to queries. So that like helps us being nimble as well beings edge is meant because then if we want to improve a feature later on, we just have to focus on one API, improve it. Like if we want to improve the performance of it, we want to improve the response times we want to improve how it’s working. You can focus on an API focus on that script, improve it. And also that kind of gives you more redundancy as well. So if something is going wrong, it’s going wrong in a particular API, and it’s not affecting everything else was Yeah.
Michael:
Yep, that’s great. Cool. Last thing I’ll say is if anybody’s interested in being part of our beta MHP launch, go to bionic WP comm just enter your email and you can be added to that list and we will let you know when we released that. I hope to have some fun. You know, sooner than later, I should let Abdul Abdul, I’ll let you before I put my foot in my mouth. What date? Do you think we could have people on the board test it in a very
Abdul:
basic version, I think the idea is that when you go for the intensive and in July when you’re going there, that’s idea that the platform is open enough there to start getting people, I would say like middle of July, or the third week of July, where people can start coming in. Like we will have a very big warning there that this is a very actively developed product. So there might be features that are things that you might see today, which might not be available two days later when we kind of work on it. But exactly, the idea is that we want to start getting because August is the month where we want to be much more stable. So if you want to do that by end of August, we need at least one month of user feedback for that so we will look at somewhere between mid and July.
Michael:
Cool. Awesome
Abdul:
That that anime video the date that you had in mind?
Michael:
Sure does. I mean, I have no, you know, I think that’s right in line. And I think, you know, you mentioned this technology stack. I think we should probably talk about that at some point and talk about, you know, how we’re building this and what we’re seeing and whatnot. So yeah, I think we are good there. And that’ll wrap it up for the week of June 19. We are putting it in the books. That’s it. Go ahead and sign up when if you want to see be part of via WPS first launch, love customer feedback in that space. I’m Michael. He’s a dual Have a great day.