Anti-Patterns Layer 2: Design Choices Core Question Is this pattern hiding a design problem? When reviewing code: - Is this solving the symptom or the cause? - Is there a more idiomatic approach? - Does this fight or flow with Rust? --- Anti-Pattern → Better Pattern | Anti-Pattern | Why Bad | Better | |--------------|---------|--------| | everywhere | Hides ownership issues | Proper references or ownership | | in production | Runtime panics | , , or handling | | when single owner | Unnecessary overhead | Simple ownership | | for convenience | UB risk | Find safe pattern | | OOP via | Misleadi…