Topic
Clean Code
Learn Clean Code as a connected topic across chapters, concepts, simulations, and interview reasoning.
10 Concepts5 Articles1h 6m
Overview
Learn Clean Code as a connected topic across chapters, concepts, simulations, and interview reasoning.
How this topic helps
Java
Software Engineering
Solid Principles
Architecture
Learning Path in this Topic
Series that contain articles from Clean Code. Select a path to filter the article list.
Articles
5 matched articles
Article 1Understanding KISS, YAGNI, and DRY: Key Software Development PrinciplesTLDR
TLDR: KISS (Keep It Simple), YAGNI (You Aren't Gonna Need It), and DRY (Don't Repeat Yourself) are the three most universally applicable software engineering mantras. They share a common enemy: 15 minArticle 2Simplifying Code with the Single Responsibility PrincipleTLDR
TLDR: The Single Responsibility Principle says a class should have only one reason to change. If a change in DB schema AND a change in email format both require you to edit the same class, that 11 minArticle 3Interface Segregation Principle: No Fat InterfacesTLDR
TLDR: The Interface Segregation Principle (ISP) states that clients should not be forced to depend on methods they don't use. Split large "fat" interfaces into smaller, role-specific ones. A Rob14 minArticle 4How the Open/Closed Principle Enhances Software DevelopmentTLDR
TLDR: The Open/Closed Principle (OCP) states software entities should be open for extension (add new behavior) but closed for modification (don't touch existing, tested code). This prevents new 13 minArticle 5Dependency Inversion Principle: Decoupling Your CodeTLDR
TLDR: The Dependency Inversion Principle (DIP) states that high-level business logic should depend on abstractions (interfaces), not on concrete implementations (MySQL, SendGrid, etc.). This let13 min