Anand Kulkarni
👤 PersonAppearances Over Time
Podcast Appearances
I'm optimistic that we will continue to stay in front on this specific set of challenges and we'll do our best to keep delivering in the way we have for our customers.
I'm optimistic that we will continue to stay in front on this specific set of challenges and we'll do our best to keep delivering in the way we have for our customers.
I'm optimistic that we will continue to stay in front on this specific set of challenges and we'll do our best to keep delivering in the way we have for our customers.
Before we went all the way in on modernization, there was this persistent debate on how deep we wanted to go in supporting Greenfield application creation versus requirements modernization in Brownfield. We built quite a bit of a product line that we ultimately killed, which was a visual drag and drop low code editor. It was cool.
Before we went all the way in on modernization, there was this persistent debate on how deep we wanted to go in supporting Greenfield application creation versus requirements modernization in Brownfield. We built quite a bit of a product line that we ultimately killed, which was a visual drag and drop low code editor. It was cool.
Before we went all the way in on modernization, there was this persistent debate on how deep we wanted to go in supporting Greenfield application creation versus requirements modernization in Brownfield. We built quite a bit of a product line that we ultimately killed, which was a visual drag and drop low code editor. It was cool.
It ran on top of your code base and it ran on top of your requirements. But ultimately, our customers did not care about that. Not in the least. They said, there's a lot of low-code tools out there. We're excited about Crowdbotics, not because it's low-code, but because you are able to generate requirements really quickly. And I think there was this idea, we had this sunk cost fallacy.
It ran on top of your code base and it ran on top of your requirements. But ultimately, our customers did not care about that. Not in the least. They said, there's a lot of low-code tools out there. We're excited about Crowdbotics, not because it's low-code, but because you are able to generate requirements really quickly. And I think there was this idea, we had this sunk cost fallacy.
It ran on top of your code base and it ran on top of your requirements. But ultimately, our customers did not care about that. Not in the least. They said, there's a lot of low-code tools out there. We're excited about Crowdbotics, not because it's low-code, but because you are able to generate requirements really quickly. And I think there was this idea, we had this sunk cost fallacy.
We had spent so much time investing into this particular line of business, and we were excited by what we thought the technology potential was, that we did not listen to our customers quickly enough. What we should have done was made the difficult decision early to mix that product, to drive focus inside the organization and shut down the studio product line sooner. That was a mistake.
We had spent so much time investing into this particular line of business, and we were excited by what we thought the technology potential was, that we did not listen to our customers quickly enough. What we should have done was made the difficult decision early to mix that product, to drive focus inside the organization and shut down the studio product line sooner. That was a mistake.
We had spent so much time investing into this particular line of business, and we were excited by what we thought the technology potential was, that we did not listen to our customers quickly enough. What we should have done was made the difficult decision early to mix that product, to drive focus inside the organization and shut down the studio product line sooner. That was a mistake.
We should have done that. And I think with experience, now we know focus is the key that drives you at scale in ways that are much harder if you decide to try and do everything.
We should have done that. And I think with experience, now we know focus is the key that drives you at scale in ways that are much harder if you decide to try and do everything.
We should have done that. And I think with experience, now we know focus is the key that drives you at scale in ways that are much harder if you decide to try and do everything.
We're all in on code to spec right now. When we look at the future of how this thing's expanding, today we're supporting a lot of mainframe code, COBOL, FORCRAN, some stuff like PS1, and some specialized systems, and then lots of cloud code, .NET, Java, PHP, even modern stuff like Django Rails node, all of which is being plugged into Gradbotics Processing.
We're all in on code to spec right now. When we look at the future of how this thing's expanding, today we're supporting a lot of mainframe code, COBOL, FORCRAN, some stuff like PS1, and some specialized systems, and then lots of cloud code, .NET, Java, PHP, even modern stuff like Django Rails node, all of which is being plugged into Gradbotics Processing.
We're all in on code to spec right now. When we look at the future of how this thing's expanding, today we're supporting a lot of mainframe code, COBOL, FORCRAN, some stuff like PS1, and some specialized systems, and then lots of cloud code, .NET, Java, PHP, even modern stuff like Django Rails node, all of which is being plugged into Gradbotics Processing.
We're excited to continue to expand those frameworks that we support and excited to support a broader set of types of customers and types of activities within the SDLC. Our bread and butter is still modernization. It's the part that most companies end up coming to us to support.
We're excited to continue to expand those frameworks that we support and excited to support a broader set of types of customers and types of activities within the SDLC. Our bread and butter is still modernization. It's the part that most companies end up coming to us to support.