Olly Headey

Yeah. I mean, that's a good question, right? Because, well, I'm not kind of setting up a big SaaS business right now. But if I was, would I use...

Yeah. I mean, that's a good question, right? Because, well, I'm not kind of setting up a big SaaS business right now. But if I was, would I use...

use rails i mean me personally if i was like a founder founder cto again i probably would mainly because that's like all i know and i'm kind of institutionalized in rails right so there's that but i still don't think it would be a bad choice i think it would be a good choice because um you know as you know you can build pretty much anything you need to with rails certainly good enough and certainly in the kind of

use rails i mean me personally if i was like a founder founder cto again i probably would mainly because that's like all i know and i'm kind of institutionalized in rails right so there's that but i still don't think it would be a bad choice i think it would be a good choice because um you know as you know you can build pretty much anything you need to with rails certainly good enough and certainly in the kind of

B2B SaaS space, of course, like that, which is, you know, but that said, you know, it depends what you're building. If you're, you know, if it's a consumer app, are you going to be able to do what you need to do on the front end with, you know, Rails stimulus? Is that, you know, good enough? Or do you actually need to lean on the community of more JavaScript stuff?

B2B SaaS space, of course, like that, which is, you know, but that said, you know, it depends what you're building. If you're, you know, if it's a consumer app, are you going to be able to do what you need to do on the front end with, you know, Rails stimulus? Is that, you know, good enough? Or do you actually need to lean on the community of more JavaScript stuff?

whether that's React or Vue or whatever else. I mean, you can still use Rails on the backend, but are you then moving into a different architecture driven because of your needs on the front end? I mean, maybe that would be a different consideration. I think at one level, I honestly don't think it really matters because technology is not usually...

whether that's React or Vue or whatever else. I mean, you can still use Rails on the backend, but are you then moving into a different architecture driven because of your needs on the front end? I mean, maybe that would be a different consideration. I think at one level, I honestly don't think it really matters because technology is not usually...

The thing that kills businesses, it honestly doesn't usually matter. The main problems with businesses are product market fit. You've built something and no one wants it, or you've marketed it wrong, or you can't get the distribution. That's usually the problem, not tech. Businesses don't usually fail because someone picked Rails or someone picked TypeScript or whatever.

The thing that kills businesses, it honestly doesn't usually matter. The main problems with businesses are product market fit. You've built something and no one wants it, or you've marketed it wrong, or you can't get the distribution. That's usually the problem, not tech. Businesses don't usually fail because someone picked Rails or someone picked TypeScript or whatever.

That doesn't seem to be the... a pattern. So I don't think it really matters. But what I do think is interesting, so I do kind of talk to a lot of startups, done some kind of like investing and stuff, but, you know, and generally in the startup community, I'm virtually non-use rails. In fact, maybe none that I've spoken to that is.

That doesn't seem to be the... a pattern. So I don't think it really matters. But what I do think is interesting, so I do kind of talk to a lot of startups, done some kind of like investing and stuff, but, you know, and generally in the startup community, I'm virtually non-use rails. In fact, maybe none that I've spoken to that is.

Whereas React on the front end and something on the back end that is typically Node-type script, maybe Python, is the prevalent tech of today, which I find quite fascinating. But these teams move fast. They get stuff done.

Whereas React on the front end and something on the back end that is typically Node-type script, maybe Python, is the prevalent tech of today, which I find quite fascinating. But these teams move fast. They get stuff done.

you know just like we do with rails so you know but it's arguably a bit more is it more complicated it feels more complicated to me but then you know at the same time companies building on cloud tech as well right and they're just leveraging serverless to do a whole manner of cool things um which you know there are legit use cases for doing that kind of stuff

you know just like we do with rails so you know but it's arguably a bit more is it more complicated it feels more complicated to me but then you know at the same time companies building on cloud tech as well right and they're just leveraging serverless to do a whole manner of cool things um which you know there are legit use cases for doing that kind of stuff

But at some level, I don't think it really matters. I think Rails is still a brilliant choice. I would do that. But again, that's because I'm probably institutionalized. But I wouldn't go and learn new tech just so I could build unless it was for a specific advantage. If you were doing some kind of AI stuff and you must use Python, then sure, do that.

But at some level, I don't think it really matters. I think Rails is still a brilliant choice. I would do that. But again, that's because I'm probably institutionalized. But I wouldn't go and learn new tech just so I could build unless it was for a specific advantage. If you were doing some kind of AI stuff and you must use Python, then sure, do that.

It's a good question. I was doing some stuff earlier this year that did kind of touch on, it was like, it was to do with image categorization, photographs, trying to kind of categorize photographs. And I did, I mean, I was using APIs to do that, like Microsoft APIs. They didn't support Ruby out of the box. They don't, you know, they have JavaScript, I can't remember, JavaScript, Python, Java,

It's a good question. I was doing some stuff earlier this year that did kind of touch on, it was like, it was to do with image categorization, photographs, trying to kind of categorize photographs. And I did, I mean, I was using APIs to do that, like Microsoft APIs. They didn't support Ruby out of the box. They don't, you know, they have JavaScript, I can't remember, JavaScript, Python, Java,