Clean Code

Choose meaningful names for variables, constants, properties, and data containers using descriptive nouns; use verbs for functions and classes like User or RequestBody.

Master naming variables, constants, and properties by examining bad, okay, and good names for a user object, including specific choices like user, customer, and isValid or isCorrect.

Name functions and methods by describing the operation they perform or their boolean result, using clear forms such as getUser, response.send, isPaid, and getUserByEmail.

Learn to name classes by describing the instantiated object, using clear, non-redundant names like user or product, avoid redundant suffixes such as DatabaseManager, and prefer instantiated types over static utilities.

This lecture teaches clean code naming by refactoring a point and rectangle example, promoting origin, width, height, and getArea, and renaming end_points to print_coordinates.

Avoid unnecessary comments and rely on self-explanatory names to improve readability. Delete redundant, misleading, or commented-out code, and use version control to recover changes.

Enhance code readability and understandability through vertical and horizontal formatting, following language-specific rules and general style guides for consistent indentation and spacing.

Explore how language-specific rules govern function ordering and execution, contrasting JavaScript's ability to call a function before its definition with Python's need to define before use.

Refactor this file by cleaning comments, removing dividers, clarifying warnings, and tightening spacing to improve readability, maintainability, and proper error handling.

Minimize function parameters to keep calls easy to understand, starting with no parameters, then one, two, or three where appropriate, and avoid more than three unless necessary.

Refactor multi-argument functions into a single argument object to improve readability and reduce order errors. Use a data container like a map or object to extract values by key.

Learn how levels of abstraction guide function responsibilities, keeping low-level details near the function name and avoiding mixing abstraction levels in code such as emailIsValid and saveUser.

Use two rules of thumb to decide when to split a function: extract blocks that implement the same functionality into a new method, and extract code that requires more interpretation.

Learn to write DRY code by splitting functions to boost reusability and avoid repeating yourself. Identify non-dry patterns like copy-paste and applying the same changes in multiple places.

Keep functions pure by ensuring the same input always yields the same output, minimize side effects, and name functions to signal when side effects are expected.

Discover how unit testing and test-driven development promote clean code by breaking complex functions into small, testable units and avoiding unwanted side effects.

Inverts the checking logic by first identifying the transaction method (credit card, PayPal, or plan) and then processing payments or refunds in specialized functions.

Explore polymorphism as an alternative to duplicate if checks and learn to split code into focused functions and data, util, and processing folders for a lean, clean codebase.

This lecture demonstrates polymorphism with classes, introducing a base delivery class and specialized express, insured, and standard deliveries, using a factory to instantiate the right type and remove if checks.

Apply the single-responsibility principle in clean code to keep classes small and focused, so changes occur for one reason, separating data generation from PDF creation.

Apply what you learned by building demo projects and using it in your day-to-day work to reinforce a solid foundation in clean code.