Dave Kimura

Hi, everyone. Welcome to another episode of Ruby Rogues. I'm David Kimura. And today on our panel, we have Matt Smith. Hello. Luke Sutters.

Hi, everyone. Welcome to another episode of Ruby Rogues. I'm David Kimura. And today on our panel, we have Matt Smith. Hello. Luke Sutters.

And we have a special guest, Kyle D'Oliveira. Did I say that right?

And we have a special guest, Kyle D'Oliveira. Did I say that right?

D'Oliveira.

D'Oliveira.

So Kyle, would you mind telling us a bit about who you are, who you work for, and some of the things that you're doing?

So Kyle, would you mind telling us a bit about who you are, who you work for, and some of the things that you're doing?

Yeah, absolutely. One thing that kind of rings true is you always have to think about scalability when you're developing, but don't actually write for scalability when you're developing. So keep it in the back of your head saying, is this going to come back and bite me later? Or is it a really non-issue?

Yeah, absolutely. One thing that kind of rings true is you always have to think about scalability when you're developing, but don't actually write for scalability when you're developing. So keep it in the back of your head saying, is this going to come back and bite me later? Or is it a really non-issue?

I remember one time I had a situation where I was storing just three kilobytes of data in a database. And I thought, okay, this is going to get used a little bit. They were images. So you can kind of see where this is going. I'm like, That's not a big deal. It's only three kilobytes. But unexpectedly, the consumers loved the feature that it was supporting.

I remember one time I had a situation where I was storing just three kilobytes of data in a database. And I thought, okay, this is going to get used a little bit. They were images. So you can kind of see where this is going. I'm like, That's not a big deal. It's only three kilobytes. But unexpectedly, the consumers loved the feature that it was supporting.

And now that single table is over 30 gigabytes. And it has millions upon millions of records. I'm like, oh, that was unexpected. But I guess that's kind of where I did not think of scale at the time. or proper way. So introducing that kind of technical debt kind of painted us in a corner because now transitioning away from that model is going to be a pain when you're dealing with that much data.

And now that single table is over 30 gigabytes. And it has millions upon millions of records. I'm like, oh, that was unexpected. But I guess that's kind of where I did not think of scale at the time. or proper way. So introducing that kind of technical debt kind of painted us in a corner because now transitioning away from that model is going to be a pain when you're dealing with that much data.

So you gave a talk last year about death by 1,000 commits. Could you give us a high-level overview of that talk and kind of some of the things it entails?

So you gave a talk last year about death by 1,000 commits. Could you give us a high-level overview of that talk and kind of some of the things it entails?

Right. And so would you mind also explaining what technical debt is? What would you consider technical debt? And what are some things that you would maybe not consider technical debt? Kind of like some debusting myths about technical debt.

Right. And so would you mind also explaining what technical debt is? What would you consider technical debt? And what are some things that you would maybe not consider technical debt? Kind of like some debusting myths about technical debt.

Mm-hmm. Yeah, I definitely have to agree with that. So what are some of the real world examples that you guys have experienced over your years where at the time you made a decision and you or the team thought like, this was a great choice. This is the right way to do it. But then later you found that it became more troublesome or more of a headache than it was worth.

Mm-hmm. Yeah, I definitely have to agree with that. So what are some of the real world examples that you guys have experienced over your years where at the time you made a decision and you or the team thought like, this was a great choice. This is the right way to do it. But then later you found that it became more troublesome or more of a headache than it was worth.