Luke Stutters

My documentation suffered for it, I must admit. Now my attitude is just, oh, they can just aless the class and see what's going on, man.

My documentation suffered for it, I must admit. Now my attitude is just, oh, they can just aless the class and see what's going on, man.

Can I ask you about, can we turn back the clock and ask you about Rails 0? Oh, it's been a long, long time since I've worked on Rails 0. I can try to answer questions, but... So it sounds like you've been on a bit of a journey with scaling things up. What did you do before Rails 0?

Can I ask you about, can we turn back the clock and ask you about Rails 0? Oh, it's been a long, long time since I've worked on Rails 0. I can try to answer questions, but... So it sounds like you've been on a bit of a journey with scaling things up. What did you do before Rails 0?

That is the correct answer. There is no other system. I ask because we were talking about the N plus one queries. And my complaint is that Rails makes it too easy to do n plus one queries, because if you just kind of follow all the guides, that's what you get. If you kind of do a dot all to each, then you're going to be there for a while.

That is the correct answer. There is no other system. I ask because we were talking about the N plus one queries. And my complaint is that Rails makes it too easy to do n plus one queries, because if you just kind of follow all the guides, that's what you get. If you kind of do a dot all to each, then you're going to be there for a while.

And you start noticing that when you start getting into a few thousand objects. So you can be sitting there prototyping something and think, this is great. And then when people start using it, you drop it in. That's when you start hitting these gotchas. But I think people forget that. what the bad old days were before you had the Rails tooling.

And you start noticing that when you start getting into a few thousand objects. So you can be sitting there prototyping something and think, this is great. And then when people start using it, you drop it in. That's when you start hitting these gotchas. But I think people forget that. what the bad old days were before you had the Rails tooling.

The amount of time it took when you had to write your own queries was really quite significant. And you mentioned enterprise Java. There's not a whole lot of object relation mapping going on in that. So it is a double-edged sword. When you're operating at the scale you do, what are the parts of Rails that start to bite?

The amount of time it took when you had to write your own queries was really quite significant. And you mentioned enterprise Java. There's not a whole lot of object relation mapping going on in that. So it is a double-edged sword. When you're operating at the scale you do, what are the parts of Rails that start to bite?

What do you think of that DHH guy? He's a bit of a weirdo, isn't he? Don't answer that. Trust me. No, I love DHH. He did a book quite a few years ago called Rework, which was prophetic, really, in the current situation about working from home. He did a RailsConf keynote, I think it was, a couple of years ago. where he said that at Basecamp, they have never had a DBA.

What do you think of that DHH guy? He's a bit of a weirdo, isn't he? Don't answer that. Trust me. No, I love DHH. He did a book quite a few years ago called Rework, which was prophetic, really, in the current situation about working from home. He did a RailsConf keynote, I think it was, a couple of years ago. where he said that at Basecamp, they have never had a DBA.

So they've never employed a person whose job it was to administer the database. This is something which Rails has just magically scaled up and the databases are scaled up. Are you in the same situation? Have you never employed a DBA for your very large Rails databases?

So they've never employed a person whose job it was to administer the database. This is something which Rails has just magically scaled up and the databases are scaled up. Are you in the same situation? Have you never employed a DBA for your very large Rails databases?

Yeah, I mean, the way DHH presented it, it was kind of this is a necessary evil mind was to have a database specialist. Instead, Rails enables developers to kind of handle this themselves and not just kind of blame the database man or woman. when the thing goes wrong. Surely as a company gets bigger, you have more specialised roles and not less specialised roles.

Yeah, I mean, the way DHH presented it, it was kind of this is a necessary evil mind was to have a database specialist. Instead, Rails enables developers to kind of handle this themselves and not just kind of blame the database man or woman. when the thing goes wrong. Surely as a company gets bigger, you have more specialised roles and not less specialised roles.

It's a really quite interesting situation. I don't know what it means for the DBAs, but I think there's definitely more database work out there. But I think because Rails just makes it so easy to work with databases at scale, that you kind of tend to hit that stage much, much later on.

It's a really quite interesting situation. I don't know what it means for the DBAs, but I think there's definitely more database work out there. But I think because Rails just makes it so easy to work with databases at scale, that you kind of tend to hit that stage much, much later on.

Yeah. Listen to this. Listen to this. Can you hear that? I can't hear anything. That is the sound of me signing up for DriftingRuby.com, which is a quite excellent series of Railscasts, including the excellent From jQuery to ES6 episode. I am a notorious jQuery user, almost an unrepentant one. But Drifting Ruby has let me see the light, and I'm a newly reformed character.

Yeah. Listen to this. Listen to this. Can you hear that? I can't hear anything. That is the sound of me signing up for DriftingRuby.com, which is a quite excellent series of Railscasts, including the excellent From jQuery to ES6 episode. I am a notorious jQuery user, almost an unrepentant one. But Drifting Ruby has let me see the light, and I'm a newly reformed character.