Challenge 3: mongosh or Compass? — Possible Solution
====================================================================

(a) Exploring an unfamiliar database's document shapes for the first time
    -> RECOMMEND: Compass.
    Justification: when you don't yet know what a database's
    documents look like, visually browsing collections, expanding
    nested fields, and seeing real example documents rendered clearly
    is exactly what a GUI is good at — it's much faster to build an
    intuitive picture of unfamiliar data by looking at it visually
    than by running exploratory find() queries in a shell one at a
    time and reading raw JSON output.

(b) Writing a deploy script that seeds some initial data automatically
    -> RECOMMEND: mongosh.
    Justification: a deploy script needs to run unattended, repeatably,
    and be checked into version control as actual code — mongosh
    commands (or a JavaScript file run through it) are inherently
    scriptable and can be automated as part of a deployment pipeline.
    Compass is a GUI meant for a human clicking through it in real
    time; it isn't something a deploy script could reasonably drive
    programmatically.

WHY THIS WORKS AS AN ANSWER
------------------------------
The deciding factor each time is WHO (or what) is actually doing the
work: a human visually exploring something unfamiliar benefits from
Compass's visual browsing, while an automated, repeatable process
needs mongosh's scriptability. Neither tool is universally "better" —
this is the same "right tool for the specific task" theme that runs
throughout this course.