Matt Rickard

What I mean is the emotional tie to the code.

What I mean is the emotional tie to the code.

I wonder if it speaks to confidence in yourself to go psychological. Like to feel like you shouldn't or can't delete it is having less confidence in yourself that you could rewrite it better. You know what I mean?

I wonder if it speaks to confidence in yourself to go psychological. Like to feel like you shouldn't or can't delete it is having less confidence in yourself that you could rewrite it better. You know what I mean?

Like you want to hold on to it because maybe you're less confident that you – and so maybe, Jared, to your point, and maybe a hat tip to you might be that you're highly confident in your abilities to rewrite the code better. Maybe I'm overconfident. Overly confident, high confidence, say it how you like. But like it leads maybe to a lack of or a high degree of confidence potentially. Maybe. Yeah.

Like you want to hold on to it because maybe you're less confident that you – and so maybe, Jared, to your point, and maybe a hat tip to you might be that you're highly confident in your abilities to rewrite the code better. Maybe I'm overconfident. Overly confident, high confidence, say it how you like. But like it leads maybe to a lack of or a high degree of confidence potentially. Maybe. Yeah.

Finding it might be challenging, though. I suppose if you can code search even history, you could.

Finding it might be challenging, though. I suppose if you can code search even history, you could.

Yeah. It's noise. As somebody who is somewhat of a digital pack rat... I can empathize with the person who has a challenge in deleting it. Not because I find it useful or that I'm emotionally tied to it, but what if I wanted to reference it? What if this could be useful someday? Right. But I also say I like to delete code. It's nice.

Yeah. It's noise. As somebody who is somewhat of a digital pack rat... I can empathize with the person who has a challenge in deleting it. Not because I find it useful or that I'm emotionally tied to it, but what if I wanted to reference it? What if this could be useful someday? Right. But I also say I like to delete code. It's nice.

Because there's some value in that, too, because you can sort of see a better future. And I think it kind of depends, really. It depends on how emotionally connected you are to it, what your confidence might be of it. If it truly, you know, if you do believe in Git, which is totally true. Like, if it's in Git. It's in there. Or even anything else. Fossil, for example.

Because there's some value in that, too, because you can sort of see a better future. And I think it kind of depends, really. It depends on how emotionally connected you are to it, what your confidence might be of it. If it truly, you know, if you do believe in Git, which is totally true. Like, if it's in Git. It's in there. Or even anything else. Fossil, for example.

The new and upcoming Git. Yeah, go agnostic. Maybe it's in Mercurial. Who knows? Maybe it is.

The new and upcoming Git. Yeah, go agnostic. Maybe it's in Mercurial. Who knows? Maybe it is.

What are the downsides? Let's say over-organizing. Is there an over to that potentially? So you want to organize it and it's an art to do so, but what about over-organizing? Can it be... fatiguing, so to speak. And the reason why I ask this is I often see this on the front end, mainly where I play most in SAS.

What are the downsides? Let's say over-organizing. Is there an over to that potentially? So you want to organize it and it's an art to do so, but what about over-organizing? Can it be... fatiguing, so to speak. And the reason why I ask this is I often see this on the front end, mainly where I play most in SAS.

I know that when SAS came about, you can always add import CSS files, for example, on the front end. But it was less common because it really, in the end, just created one big CSS file on the front end itself when you moved it along. But in SAS, I noticed that a lot of people would compartmentalize little components. And it would be like a five-line rule set for CSS in there.

I know that when SAS came about, you can always add import CSS files, for example, on the front end. But it was less common because it really, in the end, just created one big CSS file on the front end itself when you moved it along. But in SAS, I noticed that a lot of people would compartmentalize little components. And it would be like a five-line rule set for CSS in there.

And it's like, well, that could have been in the regular file. And you just find yourself itising yourself to the point where you're in so many different files that it's like, is this really helpful?

And it's like, well, that could have been in the regular file. And you just find yourself itising yourself to the point where you're in so many different files that it's like, is this really helpful?