Challenge 3: Why Not Just One Tool? — Possible Solution
====================================================================

Two genuinely different situations where Postman isn't the best fit:

1. NO GUI AVAILABLE AT ALL. Postman is a graphical desktop application
   — it doesn't help at all when working over SSH on a remote server,
   inside a minimal CI runner, or in any environment with no display.
   cURL, being a plain command-line tool, works in every one of those
   places without needing anything installed beyond what's usually
   already there.

2. REQUEST DEFINITIONS NEED TO LIVE IN VERSION CONTROL, REVIEWABLE IN
   A DIFF. Postman collections live inside Postman's own app state (or
   a separately exported/synced JSON file, which is an extra step, not
   the default). A VS Code .http file is just a plain text file sitting
   directly in the project's Git repository — it shows up naturally in
   a pull request diff, gets code-reviewed the same as any other file,
   and needs no separate export/import step to stay in sync with the
   rest of the codebase.

The broader point: Postman is genuinely excellent at what it does
(exploration, organizing many related requests, chaining them
together), but "does everything" isn't the same as "is the best tool
for every situation" — this course's four-category structure exists
specifically because each tool has a real, different strength, not
because more tools are inherently better than fewer.