How Extract Method Refactoring Cut an S3 Adapter's Readable Code by 30x

A software developer refactored an S3 document-upload adapter whose main public method, store(), buried critical logic inside deeply nested try/catch blocks and inline conditionals, making it hard to follow. The core problem was not line count but that important steps had no room to stand out amid AWS SDK setup, error handling, and logging code. Applying Martin Fowler's Extract Method technique, the developer moved roughly 90 lines of implementation detail into three intention-revealing helper methods, reducing the cognitive load in the main flow by around 30 times. The guiding principles used were limiting nesting depth to three levels and ensuring public methods read like plain-language stories of what they do. The result is a store() method that clearly narrates its own logic: upload the document, check the response, and handle errors or empty content.