law-of-demeter

Fix train wreck patterns by identifying the deepest call chains and replacing them with delegation methods on the outer object. This enforces the Law of Demeter, ensuring objects only talk to direct friends to reduce coupling.

The Law of Demeter is the principle of least knowledge, dictating that objects should only interact with immediate friends. Apply it during code reviews and refactoring when you detect deep object coupling and chained method calls across multiple languages.

Yes, you can apply the Law of Demeter across Java, Kotlin, Scala, TypeScript, Python, Ruby, Go, and Rust. Standardized guidelines and delegation patterns help minimize train wreck calls and reduce object coupling in all these languages.

The best way to reduce object coupling is to introduce delegation methods that encapsulate internal object structures. This hides implementation details and promotes direct friend communication, improving maintainability across different programming languages.

The Law of Demeter improves maintainability by minimizing dependencies between distant objects. Replacing train wreck call chains with proper delegation localizes changes, meaning modifications to an internal object are less likely to break external callers.

Avoid adding delegation methods if it results in excessive boilerplate or creates inappropriate objects merely to satisfy the Law of Demeter. If a chain represents a stable data structure or fluent interface, forcing delegation may unnecessarily complicate the design.