# Reflection: Filtering Is a Reasoning Skill, Not a Syntax Trick

## Reflection questions

1. Before this module, how would you have found "the important lines" in a huge log file?
   How does that compare to `grep`?
2. Which combination (pipe, redirect, or a specific command like `tail -f`) do you expect to
   use the most once you're doing real troubleshooting work?

## Real Ops takeaway

**"Read everything and eyeball it" does not scale — filtering does.** Every troubleshooting
framework you'll learn later in ROOT_ (starting with ROOT 02's own version, then again more
formally in ROOT 10) depends on being able to quickly narrow a huge amount of system output down
to the handful of lines that actually matter. `grep`, pipes, and redirection are the first real
tools you have for that — not a syntax exercise, a reasoning skill.

This module is complete. Continue to the next module.

## Instructor Notes

**Discussion questions for a live classroom:** question 1 often produces good answers ("I'd
just scroll and read") that make the value of filtering obvious by contrast — let students
articulate this themselves rather than stating it for them.

**Approximate timing:** 5-8 minutes live discussion; 5 minutes self-paced writing.