Challenge 2: Habitually Dismissing All Lint Warnings — Solution Walkthrough

The real risk:

Per this chapter's own warning box, some lint checks catch genuinely
meaningful bugs — a real null-pointer risk, a resource leak, an
accessibility issue actually affecting real users relying on a screen
reader — not just cosmetic style preferences. A team that dismisses
every warning without reading any of them individually has no way of
distinguishing a trivial style nitpick from a warning flagging a
genuine defect; both get treated identically and discarded the same
way.

Why this is worse than it might seem:

The habit doesn't just risk missing one particular bug — it means the
team has effectively opted out of this entire diagnostic tool's real
value, since dismissing warnings without reading them defeats the
purpose of Lint flagging anything in the first place. Any genuinely
serious issue Lint successfully identifies is guaranteed to be missed
under this habit, exactly as reliably as the trivial ones.

The correct habit instead:

Per this chapter's own material, each warning should be read and
decided on deliberately — either fixed, or suppressed explicitly with
a documented reason (via @SuppressLint or a lint baseline) — rather
than dismissed reflexively as a category, so genuine issues aren't
silently discarded alongside harmless ones.

WHY THIS WORKS AS AN ANSWER
------------------------------
This exercise directly applies this chapter's own warning box to a
realistic team habit, correctly identifying that the risk isn't just
"missing style feedback" but potentially missing a real, meaningful
bug Lint specifically exists to catch.