Challenge 2: Opening a Full IDE for a Single-Line Shell Script — Solution Walkthrough

What's happening here:

Per this chapter's own warning box, this is a real, common trap —
firing up a heavy tool out of sheer habit for a task a much lighter
tool would handle just as well. Editing a single-line shell script has
essentially none of the characteristics that would justify a full
IDE's own real cost: it's a tiny, single-file edit with no deep
language-aware tooling genuinely needed.

Why this is worth reconsidering:

IntelliJ IDEA's own startup time and resource usage are real costs
being paid here for zero corresponding benefit — none of the IDE's own
deep capabilities (project-wide refactoring, language-aware analysis,
framework tooling) apply meaningfully to editing one line of a shell
script. The developer's proficiency with the IDE doesn't change what
this specific task actually requires; it just makes the heavier tool
the reflexive, comfortable default rather than a deliberate choice.

What the chapter frames as the actual goal:

Per this chapter's own material, the real skill being built is
judgment about fit — being equally comfortable reaching for nano or a
lighter tool for a task like this one, rather than treating the most
powerful available tool as the default for everything regardless of
what a task actually needs.

WHY THIS WORKS AS AN ANSWER
------------------------------
This exercise directly applies this chapter's own warning box to a
concrete habit-driven scenario, correctly identifying the mismatch
between the tool's own real cost and the task's own minimal actual
requirements.