Challenge 2: "Serious Developers Always Edit XML Directly" — Solution Walkthrough

What's wrong with this claim:

Per this chapter's own warning box, dragging a constraint handle in
Design view and writing the equivalent app:layout_constraintTop_toTopOf-
style attribute directly in XML produce identical, real XML — there is
no hidden, lesser, or "less proper" format generated by the visual
editor. Both approaches are simply two different ways of producing
the exact same underlying file.

Why the "serious developers" framing is backwards:

Professional Android development commonly uses both views, not just
one exclusively — the visual editor for fast iteration and getting an
at-a-glance sense of the layout, and direct XML editing for precise
attribute values or sweeping bulk changes across many views at once.
Treating one as inherently more legitimate ignores that they're
complementary tools for the same file, each genuinely faster for
different kinds of tasks, rather than a beginner path and an expert
path.

A better framing to offer the teammate:

Whichever view produces the correct result faster for the specific
task at hand is the right one to use for that task — reaching for
Design view to quickly drag a button into place, then switching to
Code view to fine-tune an exact margin value, is a completely normal
and common workflow, not a compromise.

WHY THIS WORKS AS AN ANSWER
------------------------------
This exercise directly applies this chapter's own warning box to a
realistic team disagreement, correctly rejecting the "one view is more
legitimate" framing in favor of the "both are real, complementary
tools" point the chapter actually makes.