Anti-patterns to avoid in LLD - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the 'God Object' anti-pattern?

The 'God Object' anti-pattern occurs when a single class or module tries to handle too many responsibilities, making it large, complex, and hard to maintain.

beginner

Why should 'Spaghetti Code' be avoided in system design?

'Spaghetti Code' refers to code with tangled and unstructured flow, making it difficult to understand, debug, and extend, leading to poor maintainability.

intermediate

Explain the 'Golden Hammer' anti-pattern.

The 'Golden Hammer' anti-pattern happens when a familiar tool or solution is overused for all problems, even when it's not the best fit, limiting flexibility and effectiveness.

intermediate

What problems arise from the 'Not Invented Here' syndrome?

'Not Invented Here' syndrome is when teams avoid using existing solutions and prefer building their own, causing wasted effort, delays, and potentially lower quality.

beginner

Describe the 'Premature Optimization' anti-pattern.

'Premature Optimization' is when developers focus on improving performance too early, before understanding real bottlenecks, which can waste time and complicate design unnecessarily.

Which anti-pattern involves a single class handling too many tasks?

A Golden Hammer

B Spaghetti Code

C God Object

D Not Invented Here

The God Object anti-pattern is when one class or module takes on too many responsibilities.

What is a key risk of the 'Golden Hammer' anti-pattern?

A Avoiding existing solutions

B Writing tangled and unstructured code

C Optimizing too early

D Using the wrong tool for every problem

Golden Hammer means overusing a familiar tool even when it's not suitable.

Which anti-pattern describes tangled, hard-to-follow code?

A Spaghetti Code

B God Object

C Premature Optimization

D Not Invented Here

Spaghetti Code is tangled and unstructured, making it hard to maintain.

What does the 'Not Invented Here' syndrome cause?

A Using too many tools

B Avoiding existing solutions and building new ones unnecessarily

C Writing large classes

D Optimizing before measuring

Not Invented Here means rejecting existing solutions and reinventing the wheel.

Why is 'Premature Optimization' harmful?

A It wastes effort on performance before knowing real issues

B It causes code to be tangled

C It leads to large classes

D It avoids using existing tools

Premature Optimization wastes time optimizing before identifying real bottlenecks.

List and explain three common anti-patterns to avoid in system design.

Think about problems caused by too much responsibility, tangled code, and early optimization.

Describe how the 'Not Invented Here' syndrome can impact a software project.

Consider team behavior and reuse of tools.