BiteSizedChunks.comLearn one small thing at a time.

Course contentsShow

Software Engineering

327What is Refactoring?
328Why Refactor?
329When to Refactor
330When Not to Refactor
331The Two Hats of Development
332The Refactoring Safety Net
333Small Steps and Continuous Integration
334Refactoring vs Rewriting
335What Are Code Smells?
336Bloaters: Long Method
337Bloaters: Large Class and God Object
338Bloaters: Long Parameter List
339Object-Orientation Abusers: Switch Statements
340Change Preventers: Divergent Change and Shotgun Surgery
341Dispensables: Dead Code and Speculative Generality
342Dispensables: Duplicate Code
343Couplers: Feature Envy and Inappropriate Intimacy
344Couplers: Message Chains and Middle Man
345Prioritizing Code Smells
346Extract Method
347Inline Method and Inline Variable
348Rename Method and Rename Variable
349Move Method and Move Field
350Extract Class and Inline Class
351Replace Conditional with Polymorphism
352Replace Magic Numbers with Constants
353Introduce Parameter Object
354Replace Nested Conditionals with Guard Clauses
355Decompose Conditional
356Consolidate Duplicate Conditional Fragments
357Replace Temp with Query
358Red-Green-Refactor: The TDD-Refactoring Connection
359The Two Hats: Adding Function vs Restructuring
360Small Steps and Continuous Integration
361Running Tests During Refactoring
362Committing Refactorings Separately
363Opportunistic vs Planned Refactoring

Software Engineering

327What is Refactoring?
328Why Refactor?
329When to Refactor
330When Not to Refactor
331The Two Hats of Development
332The Refactoring Safety Net
333Small Steps and Continuous Integration
334Refactoring vs Rewriting
335What Are Code Smells?
336Bloaters: Long Method
337Bloaters: Large Class and God Object
338Bloaters: Long Parameter List
339Object-Orientation Abusers: Switch Statements
340Change Preventers: Divergent Change and Shotgun Surgery
341Dispensables: Dead Code and Speculative Generality
342Dispensables: Duplicate Code
343Couplers: Feature Envy and Inappropriate Intimacy
344Couplers: Message Chains and Middle Man
345Prioritizing Code Smells
346Extract Method
347Inline Method and Inline Variable
348Rename Method and Rename Variable
349Move Method and Move Field
350Extract Class and Inline Class
351Replace Conditional with Polymorphism
352Replace Magic Numbers with Constants
353Introduce Parameter Object
354Replace Nested Conditionals with Guard Clauses
355Decompose Conditional
356Consolidate Duplicate Conditional Fragments
357Replace Temp with Query
358Red-Green-Refactor: The TDD-Refactoring Connection
359The Two Hats: Adding Function vs Restructuring
360Small Steps and Continuous Integration
361Running Tests During Refactoring
362Committing Refactorings Separately
363Opportunistic vs Planned Refactoring

← Software Engineering

Lesson 330 of 1,933·10. RefactoringPro lesson

When Not to Refactor

Recognizing situations where refactoring should be avoided: broken code, tight deadlines, unclear requirements, or code slated for deletion.

This lesson is for subscribers

You've completed the free preview. Subscribe to unlock every lesson in every course.

See pricing Back to course