How deeply does Think Like a Software Engineering Manager cover refactoring?

Defines refactoring through technical-debt management and supplies review questions, but stops short of implementation techniques.

Refactoring

As explained in Think Like a Software Engineering Manager

Refactoring is the restructuring of software code to improve its internal quality without changing its externally intended behavior.

Refactoring restructures software code to improve its internal quality without changing its intended external behavior. It is one way to address technical debt created by expedient design or implementation decisions. section 12.2.3

A deadline shortcut

A team may accept duplicate code or an incomplete implementation to meet an urgent delivery date. Later, refactoring can revisit the affected architecture while preserving the feature’s intended behavior. section 12.2.3

Use these questions to identify refactoring opportunities and reduce the resulting debt:

Can duplicate code be removed? section 12.2.3
Can the code become more modular and extensible? section 12.2.3
What design blind spots, review gaps, or negative effects elsewhere might the change create? section 12.2.3

How Think Like a Software Engineering Manager covers it

Cover of Think Like a Software Engineering Manager

liveBook manning.com

Read Think Like a Software Engineering Manager on liveBook Get the book at manning.com

Also explained in

liveBook manning.com

Practices of the Python ProRefactoring is the process of changing a software system's internal design without changing its externally observable behavior.
liveBook manning.com

Infrastructure as Code, Patterns and Practices: With examples in Python and TerraformRefactoring is the disciplined restructuring of an implementation without changing its externally observable behavior.
liveBook manning.com

"Looks Good to Me"AI-assisted restructuring of code directly within a code-review workflow while proposing an immediately integrable change.
liveBook manning.com

Refactoring to RustA software-engineering process of restructuring existing code to improve qualities such as performance or maintainability without replacing the whole system.
liveBook manning.com

Shipping Go: Develop, deliver, discuss, design, and go againRefactoring is the restructuring of existing source code to improve its internal design without changing its externally observable behavior.
liveBook manning.com

The Art of CodeRefactoring is the restructuring of existing code to improve its design or clarity without changing its externally observable behavior.
liveBook manning.com

Coding with AICode refactoring is the restructuring of existing source code to improve its internal organization without changing its externally observable behavior.
liveBook manning.com

Grokking SimplicityThe systematic restructuring of existing code without changing its externally observable behavior.
liveBook manning.com

The Quick Python Book, Fourth EditionRefactoring is the systematic restructuring of existing source code to improve its internal qualities without changing its externally observable behavior.
liveBook manning.com

Software Testing with Generative AIRefactoring is the restructuring of existing source code to improve its internal design without changing its externally observable behavior.
liveBook manning.com

The Art of Unit Testing 3eRefactoring is changing the internal structure of code without changing its externally observable functionality.
liveBook manning.com

Terraform in Depth: Infrastructure as Code with Terraform and OpenTofuInternal refactoring is structural change confined within a program or module that preserves its external behavior and interfaces.
liveBook manning.com

Python How-ToRefactoring is the restructuring of existing code to improve its design or maintainability without changing its externally observable behavior.
liveBook manning.com

Bootstrapping Microservices, Second Edition: With Docker, Kubernetes, GitHub Actions, and TerraformContinuous refactoring is the repeated restructuring of software during development without changing its externally observable behavior.
liveBook manning.com

Build Financial Software with Generative AI (From Scratch)Refactoring is the restructuring of existing code to improve its organization or maintainability without changing its externally observable behavior.
liveBook manning.com

Simple Object-Oriented Design: Create clean, maintainable applicationsRefactoring is the disciplined transformation of existing software structure without changing its externally observable behavior.
liveBook manning.com

Learn AI-Assisted Python Programming, Second EditionCode refactoring is the restructuring of existing code to improve its readability or maintainability without changing its intended behavior.
liveBook manning.com

Rust Servers, Services, and AppsCode refactoring is the restructuring of existing source code without changing its externally observable behavior.
liveBook manning.com

The Well-Grounded Python Developer: How the pros use Python and FlaskRefactoring is restructuring existing code to improve its design or maintainability while preserving its intended behavior.
liveBook manning.com

Build Your Own Robot: Using Python, CRICKIT, and Raspberry PiThe systematic restructuring of existing software code without changing its externally observable behavior.
liveBook manning.com

Functional Design and Architecture: Examples in HaskellRefactoring is the disciplined restructuring of existing code without intentionally changing its externally observable behavior.

Compare how 22 books explain refactoring →

Related concepts

continuous improvementcontrasts with · Continuous improvement is an ongoing process of evaluating outcomes and making successive changes to improve a system, process, or result.
code duplicationaddresses · Code duplication is the presence of equivalent or substantially similar source code or implementation logic in multiple locations within a software system.
maintainabilityproduces · Maintainability is the degree to which software can be understood, modified, corrected, tested, repaired, or kept operational with reasonable effort over time.
complexityaddresses · Complexity is the degree of difficulty in understanding, analyzing, changing, or operating a system or problem, arising from its structure, behavior, or interacting parts.
technical debtaddresses · Technical debt is the future cost, effort, or risk created by technical choices or deferred work that make a system harder to change, maintain, or operate.
functionuses · A function is a callable program unit that performs an operation, may accept inputs, and can produce a result or side effect.

This explainer was generated by Manning's knowledge graph from the text of Think Like a Software Engineering Manager. The section links point to the parts of the book it draws on.