Boundaries¶

Status: ⏳ PENDING

The inverse of this chapter's rules — practices to recognize and avoid. Each will get a junior-level definition, a real example of the harm it causes, and the clean alternative.

Anti-Patterns to Cover¶

• Leaking third-party types throughout the codebase
• No abstraction layer over an SDK or library
• Mocking what you don't own (mocks lie when the third-party API changes)
• Tight coupling to a specific library version
• Skipping the 'learning test' for a new dependency

See the chapter README for the positive rules.