Heiki Riesenkampf

We had this bug where the longer the call got, the longer the delay in the original speech and translated speech was. We could not figure out where that came from. It was a very strange bug. I initially thought there was a memory leak, but then we're using TypeScript as our stack, so I was a little bit surprised if it had been something that I would have had control over.

And I threw a lot of weird, different things against the wall to try to chase it down. I knew that there was a feature that I added very early on, which was saving the raw audio from both calls into an audio buffer and then saving the file ourselves at the end of the call. And I never thought that such a... Simple functionality could be the cause of this delay.

And I threw a lot of weird, different things against the wall to try to chase it down. I knew that there was a feature that I added very early on, which was saving the raw audio from both calls into an audio buffer and then saving the file ourselves at the end of the call. And I never thought that such a... Simple functionality could be the cause of this delay.

And I threw a lot of weird, different things against the wall to try to chase it down. I knew that there was a feature that I added very early on, which was saving the raw audio from both calls into an audio buffer and then saving the file ourselves at the end of the call. And I never thought that such a... Simple functionality could be the cause of this delay.

But then after a month of debugging and just like scratching my head, I just removed two lines of code to build the audio buffer up during the call. And all of a sudden the delay was gone. And I was like, Damn, that was literally like should have been the first candidate to like chase down.

But then after a month of debugging and just like scratching my head, I just removed two lines of code to build the audio buffer up during the call. And all of a sudden the delay was gone. And I was like, Damn, that was literally like should have been the first candidate to like chase down.

But then after a month of debugging and just like scratching my head, I just removed two lines of code to build the audio buffer up during the call. And all of a sudden the delay was gone. And I was like, Damn, that was literally like should have been the first candidate to like chase down.

I personally feel like those things are much easier to find if you describe your problem and bug to an engineer that has nothing to do with the code. So basically rubber ducking the bug with another engineer. That's probably one of the costliest mistakes in terms of customer questions and dissatisfaction in terms of not amazing demos to date.

I personally feel like those things are much easier to find if you describe your problem and bug to an engineer that has nothing to do with the code. So basically rubber ducking the bug with another engineer. That's probably one of the costliest mistakes in terms of customer questions and dissatisfaction in terms of not amazing demos to date.

I personally feel like those things are much easier to find if you describe your problem and bug to an engineer that has nothing to do with the code. So basically rubber ducking the bug with another engineer. That's probably one of the costliest mistakes in terms of customer questions and dissatisfaction in terms of not amazing demos to date.

And that could have been totally avoided had I just approached the bug with someone with a fresh look at the problem. So yeah, collaborate more. That's maybe the ethos of the story.

And that could have been totally avoided had I just approached the bug with someone with a fresh look at the problem. So yeah, collaborate more. That's maybe the ethos of the story.

And that could have been totally avoided had I just approached the bug with someone with a fresh look at the problem. So yeah, collaborate more. That's maybe the ethos of the story.

So right now, I am heads down heavy building mode. So we are trying to get our own model out of the door and replace the existing setup while at the same time trying to improve our own infrastructure further. And so now we're on a stage where in addition to building on a daily basis, we are also trying to hire and expand the team here in New York.

So right now, I am heads down heavy building mode. So we are trying to get our own model out of the door and replace the existing setup while at the same time trying to improve our own infrastructure further. And so now we're on a stage where in addition to building on a daily basis, we are also trying to hire and expand the team here in New York.

So right now, I am heads down heavy building mode. So we are trying to get our own model out of the door and replace the existing setup while at the same time trying to improve our own infrastructure further. And so now we're on a stage where in addition to building on a daily basis, we are also trying to hire and expand the team here in New York.

Our office is located in Soho and we have an in-office culture. And so right now I'm spending quite a bit of my time on interviewing early hires. We are hopefully about to close our technical lead position and I'm interviewing a few machine learning researchers to start work on our own models.

Our office is located in Soho and we have an in-office culture. And so right now I'm spending quite a bit of my time on interviewing early hires. We are hopefully about to close our technical lead position and I'm interviewing a few machine learning researchers to start work on our own models.

Our office is located in Soho and we have an in-office culture. And so right now I'm spending quite a bit of my time on interviewing early hires. We are hopefully about to close our technical lead position and I'm interviewing a few machine learning researchers to start work on our own models.

It's really a combination of building and then hiring to just have a best in class product that would basically, let's say, never fail to wow the customer away once we get to that stage of the company.