liveBook · Manning

Pattern fragmentation

As explained in Build High Value Software Systems

The divergence of implementation patterns across features that should follow a consistent architectural or coding approach.

Pattern fragmentation occurs when features adopt different approaches to the same engineering tasks. AI-generated code can amplify it: plausible micro-decisions vary between generations and developers, even when features work individually. section 4.3.3

Variations can include:

  • Error handling with try/catch or callbacks; logging with console.log or a custom logger; validation with manual checks or a library. section 4.3.3
  • Across many features, these differences can increase onboarding difficulty, cognitive load, refactoring paralysis, and review friction. section 4.3.3
Figure 4.6 Without defined standards, each AI-generated feature adopts different patterns, creating a maintenance burden and technical debt.

Illustrates how AI-generated features can adopt different patterns without defined standards. section 4.3.3

How Build High Value Software Systems covers it

How deep it goes
Explains causes, examples, and maintenance consequences, but does not detail the proposed standard-work solution.
Examples
Contrasts try/catch with callbacks, console.log with custom logging, and manual validation with library-based validation.
How it connects
Connects AI-generated code to error handling, logging, validation, and standard work.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Build High Value Software Systems. The section links point to the parts of the book it draws on.