462: Decomposition as a key developer skill with Steve Polito

What It Covers

Steve Polito joins Joel Quenneville to explore decomposition as a fundamental developer skill, covering how to break down features into vertical slices, separate branching from business logic, and apply atomic thinking to stories, commits, and code structure.

Key Questions Answered

• •Vertical Slicing: Ship features as thin vertical slices that deliver user-facing behavior rather than horizontal layers like models then controllers. This approach informs implementation decisions through actual user interaction patterns and prevents shipping dead code that provides no immediate value to users.
• •Triangle of Separation: Apply three principles to break down complex code: write at single abstraction levels, separate branching logic from business logic into different functions, and push conditionals up the decision tree. This forces extraction of reusable functions that can be independently composed and tested.
• •Scope Reduction Tactics: Negotiate with stakeholders to simplify initial deliverables by removing modals in favor of inline displays, shipping calculated values before detailed breakdowns, or placing features behind flags. This reduces PR size from weeks to days while maintaining shippable value and enabling faster priority adjustments.
• •Churn-Complexity Analysis: Identify refactoring targets by finding files with both high complexity and high change frequency. Extract duplicated business logic into service objects based on responsibility patterns like synchronous versus asynchronous execution, or presentational versus data manipulation concerns to reduce technical debt.