Yeah totally fair question! For me it was motivated from seeing too many bloated, multi-use classes and files in enterprise codebases.
Keeping the file wider than it is long is a simple heuristic to make sure files don't grow out of their original scope and are instead split up based on separation of concerns, without just picking some arbitrary line number.
5 comments
[ 1.6 ms ] story [ 24.8 ms ] threadI don't understand why this is good or bad, can you please elaborate why this is a useful rule to follow?
Keeping the file wider than it is long is a simple heuristic to make sure files don't grow out of their original scope and are instead split up based on separation of concerns, without just picking some arbitrary line number.