>e.g. hollowing out a function body into two smaller functions and adding a tail call. Actually theres's a direct analogy there. The reason you do that is to m

>e.g. hollowing out a function body into two smaller functions and adding a tail call. Actually theres's a direct analogy there. The reason you do that is to make it easier to comprehend. It looks messy. To much info. Now imagine you have to listen to your screen reader speaking all of it. Same deal. To much, time to refactor to something more navigable.