Ayush Nwatia

Hey folks, welcome back to another episode of the Ruby Rogues podcast. This week on our panel we have Ayush Nwatia.

Hey folks, welcome back to another episode of the Ruby Rogues podcast. This week on our panel we have Ayush Nwatia.

We also have Valentino Stoll. Hey now. Charles Maxwood from Top End Devs and we have a special guest this week and that is Oli Heddy.

We also have Valentino Stoll. Hey now. Charles Maxwood from Top End Devs and we have a special guest this week and that is Oli Heddy.

No, it's fine. I should have asked, but I assumed because I think I'm smart. And then I screw stuff up because I think I'm smart. Anyway, do you want to just – you were mentioning before the show you've worked at 37 Signals. You were the CTO for Free Agent, which is a bookkeeping and financial app for businesses. Yeah. What else is there to know? What else are you famous for?

No, it's fine. I should have asked, but I assumed because I think I'm smart. And then I screw stuff up because I think I'm smart. Anyway, do you want to just – you were mentioning before the show you've worked at 37 Signals. You were the CTO for Free Agent, which is a bookkeeping and financial app for businesses. Yeah. What else is there to know? What else are you famous for?

My son wants to be a video game developer, so...

My son wants to be a video game developer, so...

Yeah, absolutely. DHH made Kamal so that he could get off the cloud.

Yeah, absolutely. DHH made Kamal so that he could get off the cloud.

Yeah, Ollie, how are you such a genius? Such a forward-thinking genius.

Yeah, Ollie, how are you such a genius? Such a forward-thinking genius.

Oh, you're going way back.

Oh, you're going way back.

And then jQuery was like the dream.

And then jQuery was like the dream.

I generally agree, but if the ongoing maintenance burden will be lessened by rewriting it and it's not like a total, hey, you're going to spend six months rewriting this piece, right? So you have to weigh all these things, but I've worked on apps where there was a new, better way of doing things. It was not terribly onerous to change it over.

I generally agree, but if the ongoing maintenance burden will be lessened by rewriting it and it's not like a total, hey, you're going to spend six months rewriting this piece, right? So you have to weigh all these things, but I've worked on apps where there was a new, better way of doing things. It was not terribly onerous to change it over.

Yeah, there was no real benefit to the users except that The next time we had to come along and maintain, touch, modify, whatever that application stuff, it was going to be much, much, much easier. And so it allowed us to deliver better and faster in the future.

Yeah, there was no real benefit to the users except that The next time we had to come along and maintain, touch, modify, whatever that application stuff, it was going to be much, much, much easier. And so it allowed us to deliver better and faster in the future.