Challenge 1: Why PyCharm Familiarity Transfers on Day One — Solution Walkthrough

Why the general experience feels familiar:

Per this chapter's own material, Android Studio and PyCharm are both
built on the same underlying platform: IntelliJ IDEA Community
Edition. The general editor experience — how code completion behaves,
most keyboard shortcuts, the refactoring tools (like Rename or Extract
Method), the overall window layout and panel arrangement, and the
plugin system — is inherited wholesale from that shared IntelliJ base,
not written independently by each IDE's own maker.

Why this isn't a coincidence or a superficial resemblance:

Because both IDEs are literally built on the same platform, a
developer who has built muscle memory around PyCharm's own shortcuts
and workflows is really building muscle memory around IntelliJ
Platform's own shortcuts and workflows — which Android Studio directly
inherits. This is a structural fact about how both IDEs are
constructed, not a matter of Google having chosen to copy some
PyCharm conventions after the fact.

What would still feel unfamiliar:

Anything Android-specific — the Layout Editor, the Profiler, the AVD
Manager — would still be genuinely new to this developer, since none
of that exists in PyCharm at all. The familiarity is specifically
scoped to the shared, inherited portion of the IDE.

WHY THIS WORKS AS AN ANSWER
------------------------------
This exercise checks that the IntelliJ-inheritance explanation from
this chapter is understood as a structural, platform-level fact —
correctly scoping which specific parts of the experience transfer and
explaining why, rather than a vague "IDEs are kind of similar" answer.