Cruft

Q: How deeply does Collaborative Software Design: How to facilitate domain modeling decisions cover cruft?

Distinguishes deliberate technical-debt cruft from unintended cruft caused by implicit design, but does not detail remediation steps.

As explained in Collaborative Software Design: How to facilitate domain modeling decisions

Poorly written, redundant, or otherwise unnecessary software code and structure that makes a system harder to change or maintain.

Cruft is poorly written or redundant code and structure that makes a system harder to change and maintain. It can prevent new functionality, slow delivery, and encourage bug-producing hacks. section 3.1.5

Cruft becomes costly when it leads to:

Inability to add new functionality. section 3.1.5
Longer implementation and push-to-production times. section 3.1.5
More bugs when developers resort to hacks. section 3.1.5

Cruft may result from conscious technical-debt decisions made to deliver value sooner, or from implicit design decisions caused by limited skill or awareness. Making decisions explicit helps expose risks, alternatives, and consequences before they become harder to manage. section 3.1.5

How Collaborative Software Design: How to facilitate domain modeling decisions covers it

Cover of Collaborative Software Design: How to facilitate domain modeling decisions

liveBook manning.com

Read Collaborative Software Design: How to facilitate domain modeling decisions on liveBook Get the book at manning.com

Also explained in

liveBook manning.com

Architecture Modernization: Socio-technical alignment of software, strategy, and structureCruft is avoidable software complexity caused by a codebase differing from its ideal structure or implementation without changing its intended functionality.

Compare how 2 books explain cruft →

Related concepts

complexityproduces · 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 debtpart of · 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.

This explainer was generated by Manning's knowledge graph from the text of Collaborative Software Design: How to facilitate domain modeling decisions. The section links point to the parts of the book it draws on.