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

Was this helpful?

  1. Introduction

About This Book

2023.01.30 (2024.04.10)

Last updated 1 year ago

Was this helpful?

As a programmer, I have always considered how the source code should look, how it is logical, and how it can reflect what it is doing.

I learned about the Clean Code book and other books on good coding practices. I collected all my knowledge in this field and added my thoughts too—you can find them on the left, under the Clean Code group. I also did a few presentations and training about clean code.

But I realized that although most programmers knew the main clean code rules, and despite them all being experienced software engineers, the source code always became very complicated. So in the recent 10 years, I tried to find the traps we often fell into and tried to understand the programming habits that may lead to overcomplicated code.

I would like to share my unusual message that we should not do many things during programming that we used to do. Of course, I try to tell what to do instead.

This is what you can read under 'clear code'. It is all based on the clean code principles. The name is explained here: .

The problem with Clean Code's name