Clear Code
  • Introduction
    • About This Book
    • Timeline
    • Software Killers
    • Billion Dollar Mistakes
    • Clear Code Overview
    • Clear Code Rules
  • Data Processing
    • Separate Data Collection And Processing
    • Create Data Models
    • Separate Use Cases
    • Data Should Be Immutable
  • Examples
    • Separate Use Cases With Data Model
  • Maintenance Cost
    • Consider the Maintenance Cost
    • The Software Exists In Time
    • Don't Feed the Monsters
  • OOP
    • Separate Data And Procedures
    • Do Not Use Inheritance
    • When To Avoid Inheritance?
    • What Is The Problem With Abstract Frameworks?
  • VARIOUS
    • The Real Single Responsibility Principle
    • The problem with Clean Code's name
    • How To Handle Warnings
    • Do Not Create Constant Collection Classes
  • Externals
    • Links
    • Quotes
    • Funny
  • Technology
    • Git Tutorials
  • Clean Code
    • Clean Code Introduction
      • Origin & Overview
      • Advanced
      • Typical Issues
    • Clean Code Outline
      • Why Clean Code?
      • Clean Code
      • Clean Code Approaches
      • Specification & Design
      • Duplication
      • Refinement & Refactoring
      • Conventions
      • Names
      • Types
      • Methods
      • Nulls and Validity Checks
      • Comments
      • Dead Code
      • Error Handling
      • Classes
      • Code Formatting
      • Unit Tests
      • Special Cases
      • Object Oriented Programming
      • General Code Smells
    • Clean Code Links
    • Clean Code TOC
    • Effective Java TOC
Powered by GitBook
On this page
  • Enterprise Software
  • Problems
  • Technical Debt

Was this helpful?

  1. Clean Code
  2. Clean Code Outline

Why Clean Code?

Enterprise Software

It is not enough to learn a programming language. We have to develop enterprise software which are:

  • Large: 100k – 1M lines

  • Long life cycle (years)

  • Complex

  • Many developer

  • Many modifications

  • Iterative development

Problems

  • Many bugs - potential bugs hiding in the code

  • Code is too complex - hard to understand

  • Code is fragile - changes causes new bugs, side effects

  • Falling productivity - low development speed

  • Unreliable, impossible estimations

  • Too much Technical Debt collected

Technical Debt

  • Invisible

  • "Should have been done"

  • "We will fix it later"

  • Result of "quick & dirty" coding

  • Poorly written code is a technical debt - "Should be written better"

The total cost of owning a mess. (Robert C. Martin)

Technical debt is the biggest risk of the development

Last updated 5 years ago

Was this helpful?