Exercise 1: Why a Restart Can Make a Recurring Problem Harder to Solve — Possible Solution
====================================================================

WHAT A RESTART ACTUALLY DOES TO THE EVIDENCE
------------------------------
Per this chapter's warn-box, "once a struggling process restarts, its
accumulated memory usage resets, its open file handles close, and its
current CPU activity vanishes - the live picture of what was actually
going wrong is gone the moment the process exits." The restart doesn't
just stop the symptom, it erases the specific state that would have
explained the symptom's actual cause.

WHY "IT WORKED" ISN'T THE SAME AS "I KNOW WHY"
------------------------------
Per this chapter, "a restart is tempting precisely because it often
works... But 'it worked' and 'I know why it was happening' are
different things entirely." A restart can relieve the symptom without
ever revealing which of the four resource categories (or something
else entirely) actually caused it.

WHY THIS MAKES A RECURRING PROBLEM HARDER, NOT EASIER
------------------------------
Per this chapter, "if the same problem returns tomorrow, you'll be
starting from zero again." Without having captured evidence the first
time, each recurrence has to be diagnosed from scratch, rather than
building on what was learned last time - the opposite of what checking
first would have provided.

WHY THIS WORKS AS AN ANSWER
------------------------------
It explains specifically what evidence a restart destroys (memory
state, open file handles, current CPU activity), and connects that
loss to why a recurring problem becomes harder to diagnose over time
rather than just asserting that restarting is "bad practice" without
justification.