liveBook · Manning

Antipattern

Also called anti-pattern

An antipattern is a recurring approach to solving a problem that may appear reasonable but tends to produce undesirable or counterproductive results in a given context.

How 5 Manning books explain it

Idiomatic Rust

An antipattern is a commonly recognized programming practice that is harmful or ineffective in particular contexts or circumstances.

How it is used
Flags Rust practices worth reconsidering when they threaten safety, efficiency, or maintainability.
How deep it goes
Defines the term and surveys common misuses with alternatives, while treating rules as contextual rather than absolute.
Examples
Uses `unwrap()`, `unsafe`, excessive `clone()`, `Deref`-based polymorphism, globals, and smart-pointer misuse as cases.
What you can do after
Evaluate/understand when a Rust practice warrants an alternative and when its context justifies an exception.

Read how Idiomatic Rust explains antipattern →

The Art of Unit Testing 3e

An antipattern is a commonly used approach that appears reasonable but produces undesirable consequences or problems.

How it is used
Identifies testing approaches that seem convenient but weaken trust, maintainability, or release confidence.
How deep it goes
Explains failure modes through worked tests and practical alternatives, rather than a formal catalog.
Examples
Uses a loop-driven name check and verifier assertions that unnecessarily fix result order, structure, or message wording.
What you can do after
Diagnose/debug with it by spotting brittle tests and replacing incidental checks with focused assertions on relevant behavior.

Read how The Art of Unit Testing 3e explains antipattern →

The AI Pocket Book

A commonly repeated but harmful approach that looks plausible yet tends to produce bad outcomes.

How it is used
Warns against AI-first product decisions and redirects attention to customer needs and validation.
How deep it goes
Defines the anti-pattern, explains its cause and failure mode, and suggests a customer-centric alternative.
Examples
Uses “if you build it, they will come,” prototypes, mock-ups, and the case of AI being trendy.
What you can do after
Diagnose/debug with it by checking whether a project serves customers first or just chases an AI solution.

Read how The AI Pocket Book explains antipattern →

PostgreSQL Mistakes and How to Avoid Them

An antipattern is a recurring design or implementation approach that appears reasonable but produces harmful consequences.

How it is used
Frames PostgreSQL design mistakes as recurring choices whose production consequences are costly, risky, or difficult to reverse.
How deep it goes
Explains relational JSON through storage examples and query consequences, but does not provide a complete replacement schema.
Examples
Uses jsonb account and sales tables, nested documents, and a join-heavy query with casts and JSON operators.
What you can do after
Evaluate whether JSON storage fits unforeseeable attributes or improperly replaces relational structure.

Read how PostgreSQL Mistakes and How to Avoid Them explains antipattern →

Prompt Engineering in Practice

An anti-pattern is a recurring practice or design approach that appears workable but commonly produces undesirable outcomes.

How it is used
Flags recurring prompt-management failures as early warnings teams can use to identify practices needing correction.
How deep it goes
Identifies ten recurring failure modes and pairs each with a concrete mitigation.
What you can do after
Evaluate prompt-management practices by recognizing recurring failure signals and addressing them with discipline rather than new tooling.

Read how Prompt Engineering in Practice explains antipattern →

Also covered in

What to know first

Related concepts

Questions about antipattern

What is antipattern?

An antipattern is a recurring approach to solving a problem that may appear reasonable but tends to produce undesirable or counterproductive results in a given context.

Which Manning books explain antipattern?

Idiomatic Rust, The Art of Unit Testing 3e, The AI Pocket Book, PostgreSQL Mistakes and How to Avoid Them and Prompt Engineering in Practice.

What should I know before learning antipattern?

Manning books that teach antipattern usually introduce microservice architecture, Map, workflow and design pattern first.

What kinds of antipattern are there?

Kinds of antipattern include anemic domain model, fat controller, golden hammer antipattern, test-level antipattern and ambient context.

What is antipattern a kind of?

Antipattern is a kind of design pattern. A design pattern is a reusable, general solution structure for a recurring software design problem.

What is antipattern also called?

Antipattern is also called anti-pattern.

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.