tda

The Tell Don't Ask principle in object-oriented programming mandates passing commands to objects rather than querying their state to make external decisions. It enforces encapsulation by moving decision-making logic inside the object itself to prevent anemic domain models.

Refactor feature envy and train wrecks by moving decision-making and state manipulation logic inside the relevant objects. Instead of chaining external method calls to query state, encapsulate the behavior by telling the object to perform the action directly.

Prevent anemic domain models in OOP by encapsulating behavior within your objects. Move state checks and mutations out of external client code and into the object's own methods to ensure it manages its internal data and transitions entirely.

External state checking before mutation violates encapsulation by exposing an object's internal data for external orchestration. This creates temporal coupling and anemic models, preventing the object from managing its own state transitions and validations internally.

Move decision-making logic inside an object when external code queries its state to perform actions, causing direct public field mutation or feature envy. This refactoring step encapsulates behavior and eliminates temporal coupling.

Yes, you can use this approach to refactor Python code. It guides you to transform external state checks into encapsulated methods, such as replacing external status validations with a dedicated confirm method that handles internal state transitions.