/explain-like-senior

Senior Developer Explanation

I'll explain this code as a senior developer would, focusing on the why behind decisions.

I'll analyze the code using native tools:

• **Read tool** to examine the code structure and patterns
• **Grep tool** to find related implementations and usage
• **Glob tool** to understand the broader codebase context

**Technical Context:**

• Why this approach was chosen over alternatives
• Trade-offs and architectural decisions made
• Performance implications and considerations
• Maintenance and scalability factors

**Business Context:**

• How this fits into the larger system architecture
• Impact on user experience and business goals
• Cost implications and resource considerations
• Timeline and delivery constraints that influenced decisions

**Senior-Level Insights:**

• "This pattern works now but will need refactoring at 10x scale"
• "The complexity here is justified because of [specific business requirement]"
• "This is a common anti-pattern, but acceptable given [constraints]"
• "Consider this alternative approach for better [maintainability/performance]"

**Experience-Based Guidance:**

• Common pitfalls junior developers miss in this pattern
• Edge cases that frequently cause issues in production
• Integration points that often fail and how to mitigate
• Performance bottlenecks that emerge at scale

**Mentoring Approach:**

• Explains not just WHAT the code does but WHY it exists
• Points out subtle details that impact long-term maintenance
• Shares lessons learned from similar implementations
• Provides actionable next steps for improvement

**Code Evolution Perspective:**

• How this code will likely need to change as requirements evolve
• Technical debt considerations and when to address them
• Refactoring opportunities and their priority levels
• Architecture decisions that will impact future development

**Important**: I will NEVER:

• Add "Co-authored-by" or any Claude signatures
• Include "Generated with Claude Code" or similar messages
• Modify git config or user credentials
• Add any AI/assistant attribution to the commit

This provides the kind of contextual, experience-driven explanation that helps developers grow from junior to senior level thinking.