Kyle d'Oliveira

And we need to make sure that everyone is learning as much as they can and not just blindly hoping that the DBA is going to handle it.

And we need to make sure that everyone is learning as much as they can and not just blindly hoping that the DBA is going to handle it.

Yeah, I would agree. And I think there are more specialized roles, but I think there are skills that apply to everyone. So, you know, as the company grows, you may have more specialized roles that have more specific knowledge, but I think probably with that specific knowledge comes the responsibility that they are not gatekeepers of that knowledge, right?

Yeah, I would agree. And I think there are more specialized roles, but I think there are skills that apply to everyone. So, you know, as the company grows, you may have more specialized roles that have more specific knowledge, but I think probably with that specific knowledge comes the responsibility that they are not gatekeepers of that knowledge, right?

They may be experts and they're maybe building content, but I would say part of their job is to make sure that that content is consumable by everyone. And if they're answering the same questions over and over and over, they're not doing their job to educate people on how to self-serve and do it themselves.

They may be experts and they're maybe building content, but I would say part of their job is to make sure that that content is consumable by everyone. And if they're answering the same questions over and over and over, they're not doing their job to educate people on how to self-serve and do it themselves.

And that's how we learn and grow as a community and get better is just by sharing this knowledge.

And that's how we learn and grow as a community and get better is just by sharing this knowledge.

Yeah, I agree. You don't necessarily have to have everyone customly building SQL. Active Record does a pretty good job of being an ORM that lets developers just do the things that they need to do. And there's data notifications available to easily add tooling that you don't need the DBA for.

Yeah, I agree. You don't necessarily have to have everyone customly building SQL. Active Record does a pretty good job of being an ORM that lets developers just do the things that they need to do. And there's data notifications available to easily add tooling that you don't need the DBA for.

But as things grow, there's things that Rails doesn't yet have tooling, and maybe that's something that if you have a DBA who is well-versed in Rails, maybe they can contribute back to the framework or add their own gems that can help everybody get better at working with databases.

But as things grow, there's things that Rails doesn't yet have tooling, and maybe that's something that if you have a DBA who is well-versed in Rails, maybe they can contribute back to the framework or add their own gems that can help everybody get better at working with databases.

And it doesn't necessarily invalidate their job, but their job becomes more of a knowledge producer, and they try to share that knowledge and make the community better.

And it doesn't necessarily invalidate their job, but their job becomes more of a knowledge producer, and they try to share that knowledge and make the community better.

Yeah. And I think that's, that's like the roles of the specialists, the people who have the specialized knowledge, they're probably more consultants. And, you know, you have someone who's like, I've got a really gnarly problem. I don't know what to do. Yeah. Like let, get them to like sit down and help with you. And that's a big asset that they can help with people.

Yeah. And I think that's, that's like the roles of the specialists, the people who have the specialized knowledge, they're probably more consultants. And, you know, you have someone who's like, I've got a really gnarly problem. I don't know what to do. Yeah. Like let, get them to like sit down and help with you. And that's a big asset that they can help with people.

And, you know, if that's a one-off, it's a one-off, but if they do this 10 times in a week, maybe there's education there, or maybe there's tooling. And I think it goes to pretty much any role that you ever feel like you're just throwing something over the fence. If you push that responsibility also to the developers, you can also end up with a much higher quality project.

And, you know, if that's a one-off, it's a one-off, but if they do this 10 times in a week, maybe there's education there, or maybe there's tooling. And I think it goes to pretty much any role that you ever feel like you're just throwing something over the fence. If you push that responsibility also to the developers, you can also end up with a much higher quality project.

Or use some of the gems available and have the N plus one queries just automatically avoided for you.

Or use some of the gems available and have the N plus one queries just automatically avoided for you.