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 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:

Java
Copy to clipboard
1public double calculateClickAndCollectTotal(Order order) {
2    double itemsTotal = 0;
3    for (Item item : order.getItems()) {
4        itemsTotal += item.getPrice() * item.getQuantity();
5    }
6    double shippingCost = itemsTotal > 100 ? 0 : 5;
7    return itemsTotal + shippingCost + order.getTax();
8}
9
10public double calculatePostShipmentTotal(Order order, boolean isExpress) {
11    double itemsTotal = 0;
12    for (Item item : order.getItems()) {
13        itemsTotal += item.getPrice() * item.getQuantity();
14    }
15    double shippingCost = isExpress ? itemsTotal * 0.1 : itemsTotal * 0.05;
16    return itemsTotal + shippingCost + order.getTax();
17}

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:

Java
Copy to clipboard
1public double calculateClickAndCollectTotal(Order order) {
2    double itemsTotal = calculateItemsTotal(order);
3    double shippingCost = itemsTotal > 100 ? 0 : 5;
4    return itemsTotal + shippingCost + order.getTax();
5}
6
7public double calculatePostShipmentTotal(Order order, boolean isExpress) {
8    double itemsTotal = calculateItemsTotal(order);
9    double shippingCost = isExpress ? itemsTotal * 0.1 : itemsTotal * 0.05;
10    return itemsTotal + shippingCost + order.getTax();
11}
12
13private double calculateItemsTotal(Order order) {
14    double itemsTotal = 0;
15    for (Item item : order.getItems()) {
16        itemsTotal += item.getPrice() * item.getQuantity();
17    }
18    return itemsTotal;
19}

By extracting the calculateItemsTotal method, 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:

Java
Copy to clipboard
1public double applyDiscount(double price, Customer customer) {
2    double loyaltyDiscount = customer.getLoyaltyLevel() * 0.02;
3    price *= (1 - loyaltyDiscount);
4    // Additional discounts
5    double seasonalDiscount = 0.10;
6    price *= (1 - seasonalDiscount);
7    return price;
8}

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:

Java
Copy to clipboard
1public double applyDiscount(double price, Customer customer) {
2    double loyaltyDiscount = customer.getLoyaltyLevel() * 0.02;
3    double seasonalDiscount = 0.10;
4    
5    double totalDiscount = 1 - loyaltyDiscount - seasonalDiscount;
6    price *= totalDiscount;
7    
8    return price;
9}

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:

Java
Copy to clipboard
1public boolean isEligibleForDiscount(Customer customer) {
2    boolean newCustomer = customer.getSignUpDate().isAfter(LocalDate.now().minusMonths(3));
3    return newCustomer && customer.getPurchaseHistory().size() > 5;
4}
5
6public boolean isEligibleForLoyaltyProgram(Customer customer) {
7    boolean newCustomer = customer.getSignUpDate().isAfter(LocalDate.now().minusMonths(3));
8    return newCustomer || customer.getLoyaltyLevel() > 3;
9}

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:

Java
Copy to clipboard
1public boolean isEligibleForDiscount(Customer customer) {
2    return isNewCustomer(customer) && customer.getPurchaseHistory().size() > 5;
3}
4
5public boolean isEligibleForLoyaltyProgram(Customer customer) {
6    return isNewCustomer(customer) || customer.getLoyaltyLevel() > 3;
7}
8
9private boolean isNewCustomer(Customer customer) {
10    return customer.getSignUpDate().isAfter(LocalDate.now().minusMonths(3));
11}

By creating the isNewCustomer method, 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! 😊