Five Lines of Code: How and when to refactor, Christian Clausen

\n \nIn Five Lines of Code you will learn: \n

\n
• The signs of bad code
\n
• Improving code safely, even when you don’t understand it
\n
• Balancing optimization and code generality
\n
• Proper compiler practices
\n
• The Extract method, Introducing Strategy pattern, and many other refactoring patterns
\n
• Writing stable code that enables change-by-addition
\n
• Writing code that needs no comments
\n
• Real-world practices for great refactoring
\n

\nImproving existing code—refactoring—is one of the most common tasks you’ll face as a programmer. Five Lines of Code teaches you clear and actionable refactoring rules that you can apply without relying on intuitive judgements such as “code smells.” Following the author’s expert perspective—that refactoring and code smells can be learned by following a concrete set of principles—you’ll learn when to refactor your code, what patterns to apply to what problem, and the code characteristics that indicate it’s time for a rework. \n \n