Size Matters

Explores principles for determining optimal code organization size, arguing that the ratio of module size to interface matters more than absolute size. Introduces the concept of minimizing the "cut" by keeping related code together while separating independent concerns, and discusses how physical constraints like screen dimensions can guide better design decisions. Uses examples from TigerBeetle's codebase to illustrate when files should be split or kept together based on cohesion rather than arbitrary line limits.