Kyle d'Oliveira

If you bring in three developers and they all have the same issue, that's probably when you might need to introduce some new documentation and be like, hey, here's our new developer handbook. You might want to read it.

If you bring in three developers and they all have the same issue, that's probably when you might need to introduce some new documentation and be like, hey, here's our new developer handbook. You might want to read it.

So I think the answer is both. I definitely think we still have places where our documentation drifts and then somebody notices and we're like, oh shit, we got to fix that.

So I think the answer is both. I definitely think we still have places where our documentation drifts and then somebody notices and we're like, oh shit, we got to fix that.

But we also do leverage tools like Danger, Danger.js, like GitHub, where it can look at code and it's not necessarily like a linter of basically saying like, hey, this is bad, but it can make a comment of being like, hey, you're doing something. Maybe this is related to this link over here and direct developers or whoever's reviewing to go take a look at the documentation.

But we also do leverage tools like Danger, Danger.js, like GitHub, where it can look at code and it's not necessarily like a linter of basically saying like, hey, this is bad, but it can make a comment of being like, hey, you're doing something. Maybe this is related to this link over here and direct developers or whoever's reviewing to go take a look at the documentation.

Maybe there's no changes that require there, and we definitely need to be careful about how much noise we generate. But in the case of a migration, if a developer writes a migration and then submits it, we could basically say, hey, did you add a new file to the db migrate file?

Maybe there's no changes that require there, and we definitely need to be careful about how much noise we generate. But in the case of a migration, if a developer writes a migration and then submits it, we could basically say, hey, did you add a new file to the db migrate file?

If so, make sure you're following the steps in here and make sure that it aligns and kind of point them back at the documentation, both for the writer of the pull request, but the reader. And then kind of helps make sure that things stay in sync. Not a perfect process. I think we're slowly getting better at making sure the documentation stays up to date.

If so, make sure you're following the steps in here and make sure that it aligns and kind of point them back at the documentation, both for the writer of the pull request, but the reader. And then kind of helps make sure that things stay in sync. Not a perfect process. I think we're slowly getting better at making sure the documentation stays up to date.

Yeah, actually, we are in the same situation. I think we were going to hire a DBA this year prior to the pandemic, and then I think there were some complications. But prior to that, the company has been operating for over 11 years, and I think now no DBA.

Yeah, actually, we are in the same situation. I think we were going to hire a DBA this year prior to the pandemic, and then I think there were some complications. But prior to that, the company has been operating for over 11 years, and I think now no DBA.

We definitely have some DevOps that are a little bit focused on making sure that the database is running and making sure that we've got replication set up and proper statistics. But we kind of put the onus on everyone. Like you don't have one person who is the guru of SQL. You have everyone. And so everyone tries to teach everyone these things.

We definitely have some DevOps that are a little bit focused on making sure that the database is running and making sure that we've got replication set up and proper statistics. But we kind of put the onus on everyone. Like you don't have one person who is the guru of SQL. You have everyone. And so everyone tries to teach everyone these things.

And we try to do our best to share that knowledge where we can to make everyone as experts as we can. So we've managed to go 11 years with no DBA, and I think we're only getting to wanting one now because we're trying to do really customized processes of this online schema migration stuff.

And we try to do our best to share that knowledge where we can to make everyone as experts as we can. So we've managed to go 11 years with no DBA, and I think we're only getting to wanting one now because we're trying to do really customized processes of this online schema migration stuff.

How do we make that completely automated, which is actually going to be a completely distinct system to the Rails system because we're going to want to apply it to any of our projects. Or maybe some gotchas between upgrading MySQL. There's probably some things that they might actually have really good insight into.

How do we make that completely automated, which is actually going to be a completely distinct system to the Rails system because we're going to want to apply it to any of our projects. Or maybe some gotchas between upgrading MySQL. There's probably some things that they might actually have really good insight into.

But I think our general approach is, even in that situation, we're going to have one DBA and hundreds of developers. And we want to make sure that they may have knowledge that might be useful for talking through things and sharing things, but the work is going to still fall on the developers.

But I think our general approach is, even in that situation, we're going to have one DBA and hundreds of developers. And we want to make sure that they may have knowledge that might be useful for talking through things and sharing things, but the work is going to still fall on the developers.