Notes / Low Level Design / 01 Object Oriented Design Principles / 4 Clean Code

4 — Clean Code

The clean-code habits — naming, small methods, spotting code smells, and refactoring for readability — that keep a well-principled design from decaying in practice.

· §202607241123-8 ·
low-level-designobject-oriented-design-principlesbook
Chapter Navigation
On This Page

4 — Clean Code

Purpose

[stub: clean-code]

Planned coverage:

  • Naming
  • Small Methods
  • Code Smells
  • Refactoring
  • Readability

Metadata

AuthorAmit Singh
Scopelow-level-design

Local graph

Full graph →

Related notes

1 — SOLID Principles

The five SOLID principles — Single Responsibility through Dependency Inversion — as the baseline design discipline every LLD interview answer gets measured against.

2 — GRASP Principles

The nine GRASP patterns — Information Expert, Creator, Controller, Low Coupling, High Cohesion, and more — for assigning responsibility to the right class.

3 — OO Design Heuristics

Practical heuristics beyond SOLID and GRASP — favoring composition, programming to interfaces, the Law of Demeter, Tell Don't Ask, and Command Query Separation.

Low-Level Design for MAANG Interviews

A book-shaped table of contents for LLD interview prep: OOP fundamentals through SOLID, design principles, UML, design patterns, dependency management, reliability, concurrency, domain modeling, API design, testing, refactoring, classic interview problems, advanced architecture, and performance — cross-linking Object-Oriented Programming and Patterns instead of duplicating them.
← All notes
Low Level Design notes Edit on GitHub
Next → 1 — UML Fundamentals