← Back
JetBrains TV June 23, 2026 58s

What's been your biggest gamble in software development?

Read full transcript 1 segments
  1. How did that go? How did that go? >> Uh, they said no, and then I left the >> Uh, they said no, and then I left the >> Uh, they said no, and then I left the job. job. job. >> Okay, yeah, that's reasonable. So, what >> Okay, yeah, that's reasonable. So, what >> Okay, yeah, that's reasonable. So, what was your biggest gamble in software was your biggest gamble in software was your biggest gamble in software development? development? development? >> We had this really, really bad in-house >> We had this really, really bad in-house >> We had this really, really bad in-house made tool. I decided to understand what made tool. I decided to understand what made tool. I decided to understand what goes on under the hood. goes on under the hood. goes on under the hood. >> I was trying to convince a startup where >> I was trying to convince a startup where >> I was trying to convince a startup where I used to work to move to Angular. I used to work to move to Angular. I used to work to move to Angular. >> There's a lot of coffee involved. The >> There's a lot of coffee involved. The >> There's a lot of coffee involved. The result came back, and of course, result came back, and of course, result came back, and of course, absolutely nothing matched. absolutely nothing matched. absolutely nothing matched. >> How did that go? >> How did that go? >> How did that go? >> Uh, they said no, and then I left the >> Uh, they said no, and then I left the >> Uh, they said no, and then I left the job. job. job. >> Okay, yeah, that's reasonable. >> Okay, yeah, that's reasonable. >> Okay, yeah, that's reasonable. >> Turns out when I rerun it that the >> Turns out when I rerun it that the >> Turns out when I rerun it that the result is actually reflecting the data, result is actually reflecting the data, result is actually reflecting the data, and I found a bug in the original and I found a bug in the original and I found a bug in the original software. software. software. >> The biggest gamble I made was going all >> The biggest gamble I made was going all >> The biggest gamble I made was going all in on cloud. I've been writing code in on cloud. I've been writing code in on cloud. I've been writing code since the '90s, so this was a really big since the '90s, so this was a really big since the '90s, so this was a really big change. change. change. >> company that I've worked with, >> company that I've worked with, >> company that I've worked with, integrating a GraphQL API. integrating a GraphQL API. integrating a GraphQL API. >> There were an API [clears throat] >> There were an API [clears throat] >> There were an API [clears throat] gateway in place, so we had to figure gateway in place, so we had to figure gateway in place, so we had to figure out like a lot of architectural out like a lot of architectural out like a lot of architectural constraints. constraints. constraints. >> We shouldn't have done that. >> We shouldn't have done that. >> We shouldn't have done that. >> No, for sure. >> No, for sure. >> No, for sure. >> Now, I absolutely love it. I could never >> Now, I absolutely love it. I could never >> Now, I absolutely love it. I could never go back. I love using JetBrains. Highly, go back. I love using JetBrains. Highly, go back. I love using JetBrains. Highly, highly recommend it. Um, I love the highly recommend it. Um, I love the highly recommend it. Um, I love the product.

Summary

The conversation revolves around significant gambles in software development, referencing specific technologies like an in-house tool, Angular, cloud adoption, and GraphQL. The key takeaway is that even failed gambles can lead to discovering bugs or advocating for valuable tools like JetBrains, underscoring the learning process inherent in innovation.

View original episode ↗