Thank you! Planning for a rollback strategy and not just that, but testing it out takes some time and resources. Unfortunately, you only find its value once you need it, which nobody wants. From my experience — yes, it’s totally worth it to have a rollback strategy. But keep in mind it’s more nuanced — you should have a general rollback strategy for regular code (maybe like an interface change). But then, for any critical component change, maybe in how you process some data, you need to consider how you roll back the already incurred data changes. This is the more difficult task and we sometimes discover that rolling back certain changes is not that easy and you may want to fix it going forward, rather than backwards.
Maybe this is a good topic for another article :).

Thank you for the kind words! I found a great community in Ukraine as well, I’m just now starting to explore more resources. People are highly skilled and passionate about the subject, so you can find useful and trustworthy information.