Architecture
web-development
Locality of behavior
some devs claim functions should be short so they can be single responsibility an you remmmebr what they do. Problem is then you need to hold in your head 200 smaller functions.
What "Locality of behavior" proposes is to keep loot of things together so you can track what's happening, and this may resolve to long function which sucks but better than 200 abstractions no-one will track