I am torn. On the one hand, the phrase is definitely overused. It's like "reason about" is the functional world's version of OOPs "modularity". It gets used so

I am torn. On the one hand, the phrase is definitely overused. It's like "reason about" is the functional world's version of OOPs "modularity". It gets used so much it ceases to hold meaning beyond "thing that makes our way good". On the other hand, it is clear to me that some promises do hold up. In cases where the phrase is used correctly, it means there are some questions you can answer about the code without having to execute it line-by-line in your head. That is objectively valuable, even if your only reason for reading the code in the first place is to determine which parts of it you can safely trash and replace from scratch.