Exercise 1: Same Feel, Different Fixes — Possible Solution
====================================================================

WHY BOTH FEEL EQUALLY SLOW TO A USER
------------------------------
A user experiences total page load time, not the number or shape of
the queries behind it. An 812ms single query and 51 queries totaling
780ms both add up to a broadly similar overall delay from the page's
own perspective - to someone waiting for the page, "roughly 800ms of
database time" feels the same regardless of how many individual
queries produced it.

WHY THE SINGLE SLOW QUERY NEEDS A DIFFERENT FIX
------------------------------
Per this chapter, a single slow query is fixed by "optimizing or
indexing one query" - the problem is that one specific query is
inherently expensive to execute (often, per this chapter's own EXPLAIN
section, because it's missing an index and forcing a full table scan).
Fixing it means making that one query itself faster.

WHY N+1 NEEDS A COMPLETELY DIFFERENT FIX
------------------------------
Per this chapter, N+1 is fixed by "restructuring the code so it stops
looping and issuing a query per item" - here, no individual query is
necessarily slow (each of the 51 queries might be perfectly fast on
its own); the problem is the sheer number of separate round-trips.
Indexing wouldn't help, since none of the individual queries is
inherently expensive - the fix has to change the code's own structure
to batch the work into fewer queries.

WHY THIS WORKS AS AN ANSWER
------------------------------
It explains why both scenarios produce a similar user-facing
experience despite being structurally different underneath, and names
the specific, different fix each one requires per the chapter's own
reasoning - one targets query efficiency, the other targets query
count.