Applying Clean Code Principles: Understanding DRY in TypeScript

Welcome to the very first lesson of the "Applying Clean Code Principles" course! In this lesson, we will focus on a fundamental concept in clean coding: the DRY ("Don't Repeat Yourself") principle. Understanding DRY is crucial for writing efficient, maintainable, and clean code. This principle is not just important for coding interviews but also in everyday software development. Today, we will dive deep into issues caused by repetitive code and explore strategies to combat redundancy. 🚀

Repetitive functionality in code can introduce several issues that affect the efficiency and maintainability of your software:

• Code Bloat: Repeating similar code across different parts of your application unnecessarily increases the size of the codebase. This makes the code harder to navigate and increases the chances of introducing errors.

• Risk of Inconsistencies: When similar pieces of logic are scattered across different areas, it's easy for them to become out of sync during updates or bug fixes. This can result in logic discrepancies and potentially introduce new problems.

• Maintenance Challenges: Updating code often requires modifications in multiple places, leading to increased work and a higher likelihood of errors. Redundant code makes it difficult for developers to ensure that all necessary changes have been made consistently.

To adhere to the DRY principle and avoid repeating yourself, several strategies can be employed:

• Extracting Method: Move repeated logic into a dedicated method that can be called wherever needed. This promotes reuse and simplifies updates.

• Extracting Variable: Consolidate repeated expressions or values into variables. This centralizes change, reducing the potential for errors.

• Replace Temp with Query: Use a method to compute values on demand rather than storing them in temporary variables, aiding in readability and reducing redundancy.

Consider the following problematic code snippet where repetitive logic is used for calculating the total price based on different shipping methods:

class Order {
    items: Item[];
    tax: number;

    constructor(items: Item[], tax: number) {
        this.items = items;
        this.tax = tax;
    }

    getItems(): Item[] {
        return this.items;
    }

    getTax(): number {
        return this.tax;
    }
}

class Item {
    price: number;
    quantity: number;

    constructor(price: number, quantity: number) {
        this.price = price;
        this.quantity = quantity;
    }

    getPrice(): number {
        return this.price;
    }

    getQuantity(): number {
        return this.quantity;
    }
}

function calculateClickAndCollectTotal(order: Order): number {
    let itemsTotal = 0;
    for (let item of order.getItems()) {
        itemsTotal += item.getPrice() * item.getQuantity();
    }
    let shippingCost = itemsTotal > 100 ? 0 : 5;
    return itemsTotal + shippingCost + order.getTax();
}

function calculatePostShipmentTotal(order: Order, isExpress: boolean): number {
    let itemsTotal = 0;
    for (let item of order.getItems()) {
        itemsTotal += item.getPrice() * item.getQuantity();
    }
    let shippingCost = isExpress ? itemsTotal * 0.1 : itemsTotal * 0.05;
    return itemsTotal + shippingCost + order.getTax();
}

Both methods contain duplicated logic for calculating the total price of items, making them error-prone and hard to maintain. Now, let's refactor this code.

By consolidating the shared logic into a separate method, we can eliminate redundancy and streamline updates:

function calculateClickAndCollectTotal(order: Order): number {
    let itemsTotal = calculateItemsTotal(order);
    let shippingCost = itemsTotal > 100 ? 0 : 5;
    return itemsTotal + shippingCost + order.getTax();
}

function calculatePostShipmentTotal(order: Order, isExpress: boolean): number {
    let itemsTotal = calculateItemsTotal(order);
    let shippingCost = isExpress ? itemsTotal * 0.1 : itemsTotal * 0.05;
    return itemsTotal + shippingCost + order.getTax();
}

function calculateItemsTotal(order: Order): number {
    let itemsTotal = 0;
    for (let item of order.getItems()) {
        itemsTotal += item.getPrice() * item.getQuantity();
    }
    return itemsTotal;
}

By extracting the calculateItemsTotal function, we centralize the logic of item total calculation, leading to cleaner, more maintainable code.

Let's look at another example dealing with repeated calculations for discount rates:

function applyDiscount(price: number, customer: Customer): number {
    let loyaltyDiscount = customer.getLoyaltyLevel() * 0.02;
    price *= (1 - loyaltyDiscount);
    // Additional discounts
    let seasonalDiscount = 0.10;
    price *= (1 - seasonalDiscount);
    return price;
}

Here, the discount rates are scattered throughout the code, which complicates management and updates.

We can simplify this by extracting the discount rates into variables:

function applyDiscount(price: number, customer: Customer): number {
    const loyaltyDiscount = customer.getLoyaltyLevel() * 0.02;
    const seasonalDiscount = 0.10;
    
    const totalDiscount = 1 - loyaltyDiscount - seasonalDiscount;
    price *= totalDiscount;
    
    return price;
}

Now, with the totalDiscount variable, the logic is cleaner, more readable, and allows changes in just one place. 🎉

Our final example involves temporary variables that lead to repetition:

function isEligibleForDiscount(customer: Customer): boolean {
    const newCustomer = customer.getSignUpDate().isAfter(new Date(Date.now() - 3 * 30 * 24 * 60 * 60 * 1000));
    return newCustomer && customer.getPurchaseHistory().length > 5;
}

function isEligibleForLoyaltyProgram(customer: Customer): boolean {
    const newCustomer = customer.getSignUpDate().isAfter(new Date(Date.now() - 3 * 30 * 24 * 60 * 60 * 1000));
    return newCustomer || customer.getLoyaltyLevel() > 3;
}

The variable newCustomer is used in multiple places, causing duplicated logic.

Let's refactor by extracting the logic into a method, reducing duplication and enhancing modularity:

function isEligibleForDiscount(customer: Customer): boolean {
    return isNewCustomer(customer) && customer.getPurchaseHistory().length > 5;
}

function isEligibleForLoyaltyProgram(customer: Customer): boolean {
    return isNewCustomer(customer) || customer.getLoyaltyLevel() > 3;
}

function isNewCustomer(customer: Customer): boolean {
    return customer.getSignUpDate().isAfter(new Date(Date.now() - 3 * 30 * 24 * 60 * 60 * 1000));
}

By creating the isNewCustomer function, we've simplified the code and made it more maintainable. 🚀

In this lesson, you learned about the DRY principle and strategies like Extracting Method, Extracting Variable, and Replace Temp with Query to eliminate code redundancy. These strategies help to create code that is easier to maintain, enhance, and understand. Next, you'll have the opportunity to apply these concepts in practical exercises, strengthening your ability to refactor code and uphold clean coding standards. Happy coding! 😊