Scribd Logo
Upload

Welcome to Scribd!

  • Don't Forget:: Clean Code Readable and Understandable Code

    Uploaded by

    Anurag Mishra
    20 views7 pages
    The document discusses the importance of writing clean and readable code. It states that clean code is readable, understandable code regardless of programming language or style. The core principles of clean code, such as having meaningful names and slim functions, always apply. While different programming paradigms have their own specific rules, the concepts in the course, like clean code and patterns/principles, are generally applicable. The course focuses on how to structure individual files and code, rather than project structure. Testing helps write clean code but was not the focus of the course.

    Original Description:

    Original Title

    Slides Roundup

    Copyright

    © © All Rights Reserved

    Available Formats

    PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    Report this Document
    The document discusses the importance of writing clean and readable code. It states that clean code is readable, understandable code regardless of programming language or style. The core principles of clean code, such as having meaningful names and slim functions, always apply. While different programming paradigms have their own specific rules, the concepts in the course, like clean code and patterns/principles, are generally applicable. The course focuses on how to structure individual files and code, rather than project structure. Testing helps write clean code but was not the focus of the course.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Flag for inappropriate content
    20 views7 pages

    Don't Forget:: Clean Code Readable and Understandable Code

    Uploaded by

    Anurag Mishra
    The document discusses the importance of writing clean and readable code. It states that clean code is readable, understandable code regardless of programming language or style. The core principles of clean code, such as having meaningful names and slim functions, always apply. While different programming paradigms have their own specific rules, the concepts in the course, like clean code and patterns/principles, are generally applicable. The course focuses on how to structure individual files and code, rather than project structure. Testing helps write clean code but was not the focus of the course.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Flag for inappropriate content
    of 7

    The Most Important Rule

    Don’t forget:
    Clean Code
    ==
    Readable and
    Understandable Code
    The Core Principles & Rules Always Apply!

    No matter which programming


    language or style you’re using…

    …you still want readable …you still want slim, concise …you still want
    and meaningful names functions or methods understandable code flow
    Functional vs OOP vs Procedural

    This course doesn’t focus on a specific paradigm

    Paradigm-specific rules, conventions, patterns and guides should


    also be considered

    The rules, concepts, ideas and patterns


    shown in this course apply in general!
    Clean Code and Patterns & Principles

    Patterns & Principles Clean Code

    Write code which is Write code which is readable


    maintainable and extensible & easy to understand
    Clean Code vs Clean Architecture

    Co u rse
    T h is
    Clean Code Clean Architecture

    How to write the code Where to write which code

    Focus on single problems / files Focus on the project as a whole


    Testing and TDD

    This course did not focus on testing or test-driven development

    Testing helps with writing clean code (see “Functions” section) but is not strictly
    required

    Having working tests could be considered a part of code being clean


    (because tests express how the code should be used and what the desired goal is)

    Consider diving deeper into testing and TDD as an addition to


    applying the rules and ideas conveyed in this course
    Thank You!

    You might also like