The Open-Close Principle in Software Development, Right?

With modern tooling now, if I need to change a piece of code, it's not scary to open it up. If you're building a library that is going to be used by somebody that you will never meet, as opposed to someone else in your organization, you want to think about that. But at a certain point, application of the open close principle in most contexts just devolves into decoupling. And this is, again, getting back to Dan's point about like, just write simple code, right?