Exercise 1: Fixing a Zero-Result Six-Operator Query — Possible Solution ==================================================================== THE RECOMMENDED PROCESS, PER THIS CHAPTER ------------------------------ Per this chapter's "Debugging a Zero-Result Query" section, the fix is to "remove operators one at a time - starting with whichever feels least essential to what's actually being looked for - rather than abandoning the query and starting over." This isolates exactly which specific constraint was responsible for the empty result set, one removal at a time, checking the result count after each change. WHY THIS BEATS STARTING OVER FROM SCRATCH ------------------------------ Per this chapter, most of a six-operator query's constraints are probably fine - the query fails because at least one specific condition (an overly narrow date range, an exact phrase that doesn't appear verbatim anywhere, an overly specific site scope) has no matches, not because the whole approach is wrong. Starting over from scratch discards all of that already-correct work and risks reproducing the exact same problem, since the underlying cause was never actually identified - only worked around by accident, if at all. Incrementally removing operators, by contrast, directly locates the specific broken piece so it alone can be loosened or fixed. APPLYING THE CHAPTER'S OWN PRIORITY GUIDANCE ------------------------------ Per this chapter's own worked example, the operator removed first should be "whichever feels least essential to what's actually being looked for" - often a date filter or a secondary narrowing operator (intitle:, filetype:) rather than the exact phrase or site scope that was likely the actual point of the search in the first place. Removing operators in roughly that priority order (least central first) gets to a working query faster than removing them in an arbitrary order. WHY THIS WORKS AS AN ANSWER ------------------------------ It restates the chapter's own recommended process precisely, explains the underlying reason removal-based debugging outperforms restarting (most of the query is likely already correct), and applies the chapter's own priority guidance (least essential operator first) rather than describing the process in the abstract only.