Mihri Minaz
👤 PersonAppearances Over Time
Podcast Appearances
focused on the calendar, they can also tell us like, okay, maybe there is also an event which is not on your calendar. So that critical thinking only comes when the person is thinking in a conceptual way.
So like our team is very experienced and like 16 years experience. Our backend engineer is like 17 and worked at like banking applications. So when you think about it, for us, the scalability issue is not that we would overlook on something, but we could over-engineer. So that's why we were always talking about from the beginning, are we over-engineering this?
So like our team is very experienced and like 16 years experience. Our backend engineer is like 17 and worked at like banking applications. So when you think about it, for us, the scalability issue is not that we would overlook on something, but we could over-engineer. So that's why we were always talking about from the beginning, are we over-engineering this?
So like our team is very experienced and like 16 years experience. Our backend engineer is like 17 and worked at like banking applications. So when you think about it, for us, the scalability issue is not that we would overlook on something, but we could over-engineer. So that's why we were always talking about from the beginning, are we over-engineering this?
Should we implement the feature flag for this or should we keep it easy to submit and then we can later remove this part of the code or something? I do think like at the beginning, this mindset moving really fast and then like maybe building something that like you will completely put in trash. That mindset was not easy for the team.
Should we implement the feature flag for this or should we keep it easy to submit and then we can later remove this part of the code or something? I do think like at the beginning, this mindset moving really fast and then like maybe building something that like you will completely put in trash. That mindset was not easy for the team.
Should we implement the feature flag for this or should we keep it easy to submit and then we can later remove this part of the code or something? I do think like at the beginning, this mindset moving really fast and then like maybe building something that like you will completely put in trash. That mindset was not easy for the team.
And so we had this, even I remember this conversation that like we should build it in a way that this code lasts for five years. And I'm like, no, this code shouldn't last five years. Yeah. And that mindset made us move very fast. But then, of course, at one point, there were times that, okay, we need to change our cloud provider.
And so we had this, even I remember this conversation that like we should build it in a way that this code lasts for five years. And I'm like, no, this code shouldn't last five years. Yeah. And that mindset made us move very fast. But then, of course, at one point, there were times that, okay, we need to change our cloud provider.
And so we had this, even I remember this conversation that like we should build it in a way that this code lasts for five years. And I'm like, no, this code shouldn't last five years. Yeah. And that mindset made us move very fast. But then, of course, at one point, there were times that, okay, we need to change our cloud provider.
And then, okay, now we take the time and then we try to make us independent from cloud provider. But that is something, I think, understandable from an early stage. So then you make the decision based on that.
And then, okay, now we take the time and then we try to make us independent from cloud provider. But that is something, I think, understandable from an early stage. So then you make the decision based on that.
And then, okay, now we take the time and then we try to make us independent from cloud provider. But that is something, I think, understandable from an early stage. So then you make the decision based on that.
People, when they change their job or when they have a new computer and when they try to join their next meeting and they use the shortcut and then all of a sudden they notice that the app is not there.
People, when they change their job or when they have a new computer and when they try to join their next meeting and they use the shortcut and then all of a sudden they notice that the app is not there.
People, when they change their job or when they have a new computer and when they try to join their next meeting and they use the shortcut and then all of a sudden they notice that the app is not there.
To be able to be infused in their day this much, that they take it granted almost, that it's a part of their behavior almost, that is making me proud because then they write this to me or in our community Slack that they were surprised that it's not there. And then they were like, oh, okay, I have a new computer. They changed their job.
To be able to be infused in their day this much, that they take it granted almost, that it's a part of their behavior almost, that is making me proud because then they write this to me or in our community Slack that they were surprised that it's not there. And then they were like, oh, okay, I have a new computer. They changed their job.
To be able to be infused in their day this much, that they take it granted almost, that it's a part of their behavior almost, that is making me proud because then they write this to me or in our community Slack that they were surprised that it's not there. And then they were like, oh, okay, I have a new computer. They changed their job.
So because our vision from the beginning was there is no such work tool that continuously changes