How should code be organized in modules or packages?

• A. Place all code in a single global namespace to simplify access.
• B. Keep module boundaries vague to allow flexibility.
• C. Group related functionality into cohesive modules with clear boundaries, minimal coupling, and explicit dependencies.
• D. Use many circular dependencies to maximize reuse.

Answer: (C)

Organizing code into cohesive modules with clear boundaries, minimal coupling, and explicit dependencies keeps a codebase understandable and maintainable as it grows. When each module has a focused responsibility, you can reason about, test, and change that part without unintentionally affecting others. Clear boundaries help new developers quickly grasp what each module does, and explicit dependencies make the relationships between parts visible, so you can swap implementations, mock components in tests, or evolve interfaces without breaking the whole system. Minimal coupling means modules rely on well-defined interfaces rather than shared state, reducing ripple effects when you tweak one area.

Putting all code in a single global namespace leads to naming conflicts and makes it hard to evolve or reuse parts independently. Keeping module boundaries vague gives little guidance on responsibilities, which invites muddled design and harder maintenance. Circular dependencies tie modules together in fragile loops, which complicates reasoning about flow, creates startup or load-order problems, and hampers reuse.