Challenge 3: A Senior Developer Choosing nano for a One-Line Fix — Solution Walkthrough

Why this isn't a sign of reduced skill:

Per this chapter's own warning box, the more accurate framing is the
opposite of what might first seem intuitive — confidently reaching for
nano for a quick, single-line fix, rather than firing up a heavier
tool purely out of habit, is matching tool weight to task exactly as
Chapter 1's own spectrum framing describes. A full IDE's own startup
time and general overhead would add real cost here for no real
benefit, since none of that IDE's own deeper tooling (project
awareness, language-aware completion) does anything useful for a
one-line edit to a single file.

Why this specifically demonstrates skill, not its absence:

Deliberately choosing the lightest tool that's sufficient for the
task, rather than reflexively reaching for the most powerful tool
available regardless of fit, reflects an accurate understanding of
what each tool actually costs and provides — exactly the judgment
this chapter's own warning box frames as the correct instinct, not a
shortcut taken due to unfamiliarity with better options.

What would actually indicate a problem:

If this same developer were making the identical choice out of not
knowing how to use a full IDE at all, that would be a different
situation — but the exercise describes a developer who has a "usual
full IDE" and is choosing nano anyway for this specific task, which is
precisely the deliberate, task-matched choice this chapter's warning
box describes as correct.

WHY THIS WORKS AS AN ANSWER
------------------------------
This exercise applies this chapter's own warning box to a concrete
scenario explicitly designed to look like it might be a shortcut,
correctly identifying it instead as the exact behavior the chapter
holds up as good practice.