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
  • Successive Refinement
  • Coding Cycle
  • Modifications
  • Refactoring
  • Design Patterns

Was this helpful?

  1. Clean Code
  2. Clean Code Outline

Refinement & Refactoring

Successive Refinement

  • Write a draft or "monolith" first

  • Refine/refactor it

Coding Cycle

  • Think

  • Code

  • Think again

  • Optimize/refactor

Modifications

  • Refactor first, write code after that

  • Change the "pseudo code" first, the real code after that

  • Refactor to isolate changed part

Refactoring

  • Refactoring is good, technical debt is bad

  • Refactoring is a mandatory part of the iterative development

  • Continuously refactor unclean code to clean code

  • Always refactor for changes in the requirements - "Until now the program had to do this, from now on the program has to do that"

Design Patterns

(Not part of this training. See links.)

Last updated 5 years ago

Was this helpful?