Jared Santo

The only one I can think of is Snow Leopard, which was Apple's version of macOS that was touted as having no new features, even though there were a few features in there, but it was an entire release cycle all focused on stability, refactoring, performance. And it is to this day many people's favorite version of macOS. Going back, everyone's like, yeah, Snow Leopard was awesome.

The only one I can think of is Snow Leopard, which was Apple's version of macOS that was touted as having no new features, even though there were a few features in there, but it was an entire release cycle all focused on stability, refactoring, performance. And it is to this day many people's favorite version of macOS. Going back, everyone's like, yeah, Snow Leopard was awesome.

Reminds me of something mechanics say that I learned recently. They say, if you don't schedule your maintenance, then your car will schedule it for you.

Reminds me of something mechanics say that I learned recently. They say, if you don't schedule your maintenance, then your car will schedule it for you.

Oh, is that where I read it? Okay.

Oh, is that where I read it? Okay.

Right. That test suite becomes such an asset down the road. I was just updating our dependencies today and just having test coverage where I could say, okay, here's a dependency, run the tests, everything passed, update the latest, run the tests again, everything passed. It just has a peace of mind that you're like, okay, updating that dependency did not break everything.

Right. That test suite becomes such an asset down the road. I was just updating our dependencies today and just having test coverage where I could say, okay, here's a dependency, run the tests, everything passed, update the latest, run the tests again, everything passed. It just has a peace of mind that you're like, okay, updating that dependency did not break everything.

Yeah, it's like if you don't run your unit tests, then your customers will for you just to reapply the statement.

Yeah, it's like if you don't run your unit tests, then your customers will for you just to reapply the statement.

Here's a question for you, Bert. How do you know how many dependencies is too many dependencies? Like, is there a heuristic? Where do I know that I've just jumped the shark?

Here's a question for you, Bert. How do you know how many dependencies is too many dependencies? Like, is there a heuristic? Where do I know that I've just jumped the shark?

Yeah, the tough thing about dependencies, even when you can audit, if you can and have audited and checked out the owners and the code and the whole do your due diligence, is that what we're learning over the course of years and decades is even if you do that, if you're loading your dependencies from the network, you can't trust the network and you can trust what you think you can trust today.

Yeah, the tough thing about dependencies, even when you can audit, if you can and have audited and checked out the owners and the code and the whole do your due diligence, is that what we're learning over the course of years and decades is even if you do that, if you're loading your dependencies from the network, you can't trust the network and you can trust what you think you can trust today.

You can't actually trust a year from now because the network changes. And so even if you're doing some due diligence, like you can still get bit, these so-called supply chain attacks are happening more and more often where all of a what you thought was your dependency is replaced with code that is not the same code. And that's incredibly troubling for me.

You can't actually trust a year from now because the network changes. And so even if you're doing some due diligence, like you can still get bit, these so-called supply chain attacks are happening more and more often where all of a what you thought was your dependency is replaced with code that is not the same code. And that's incredibly troubling for me.

If you select a dependency wisely, it can save you hundreds of hours of effort. So maybe one or two hours spent putting the work in is worthwhile, right?

If you select a dependency wisely, it can save you hundreds of hours of effort. So maybe one or two hours spent putting the work in is worthwhile, right?

Are these youngsters you're talking to?

Are these youngsters you're talking to?