The Maintenance Cost of Deep Drilling
What you'll learn: How passing props through many component layers creates a maintenance nightmare when requirements change.
The Real Pain Point
Prop drilling becomes a serious problem not when you write the code, but when you need to change it. Imagine you've drilled a userId prop through five components. Now your requirements change—you need to pass userRole too.
Here's what happens: you must touch every single intermediate component in the chain, even though none of them care about this new prop. Component A passes it to B, B passes it to C, C passes it to D, and finally D uses it.
The Refactoring Burden
Each modification means:
- Opening 4-5 files
- Adding the prop to each function signature
- Adding it to each intermediate
<Component {...} />call - Risk of typos or forgetting one layer
- More git conflicts if multiple developers work nearby
- Harder code reviews (5 files changed for one logical update)
This violates a key principle: components shouldn't know about data they don't use. Yet with deep drilling, intermediate components become tightly coupled to the data flow above and below them.
The Cascade Effect
Worse, this creates a cascade: if Component C now genuinely needs access to userId for its own logic, you're stuck. Changing C's behavior might break D. Every layer becomes fragile, and simple changes require careful coordination across the entire chain.
Key Takeaway: Deep prop drilling turns simple feature additions into multi-file refactoring exercises, where components that don't care about the data must be modified anyway—a clear maintenance red flag.