Clean Code - Notes 01

Clean Code: Writing Code for Humans

Pluralsight Video Course Notes

Assign booleans implicitly.

bad:

bool isGoingToLunch
if(cashInWallet > 6.00)
{
    isGoingToLunch = true;
} else {
    isGoingToLunch = false;
}

good:

bool isGoingToLunch = cashInWallet > 6.00;

Always use positive bool statements (our brains have a harder time understanding double negatives) example of a bad bool: !isNotLoggedIn

Ternary is elegant.

bad:

int registrationFee;
if (isSpeaker) registrationFee = 0;
else registrationFee = 50;

good:

int registrationFee = isSpeaker ? 0 : 50;

DRY - DON’T REPEAT YOURSELF

YAGNI - YOU AIN’T GONNA NEED IT

(don’t add unnecessary complexity you think you’ll need later)

Avoid being “Stringly” Typed.

bad:

if (employeeType == "manager")

good (enum):

if (employee.Type == EmployeeType.Manager)

Reasons:

1. Strongly typed => No typos
2. Intellisense support
3. Documents states
4. Searchable

Complex Conditionals

Bad:

if (employe.Age > 55
    && employee.YearsEmployed > 10
    && employee.IsRetired == true)
{ logic }

What question is this trying to answer?

Good (Use Intermediate Variable):

if (bool eligibleForPension = 
    employee.Age > MinRetirementAge
    && employee.YearsEmployed > 10
    && employee.IsRetired;)
{  logic   }

Much clearer intent

Complex Conditionals (again)

Bad:

// check for valid file extensions. confirm admin or active
if (fileExtension == "mp4" ||
    fileExtension == "mpg" ||
    fileExtension == "avi")  
    && (isAdmin || isActiveFile);

Favor expressive code over comments

Good:

if (ValidFileRequest(fileExtension, active))

private bool ValidFileRequest (string fileExtension, bool isActiveFile, bool isAdmin)
{
    var validFileExtensions = new List<string>() 
    { "mp4", "mpg", "avi" };
    bool validFileType = validFileExtensions.Contains(fileExtension);
    bool userIsAllowedToViewFile = isActiveFile || isAdmin;

    return validFileType && userIsAllowedToViewFile;
}

Favor Polymorphism over Enums for Behavior

Dirty:

private void LoginUser(User user)
{
    switch (user.Status)
    {
        case Status.Active:
            //logic for active users
            break;
        case Status.Inactive:
            //logic for inactive users
            break;
        case Status.Locked:
            //logic for locked users
            break;
    }
}

Clean:

private void LoginUser(User user)
{
    user.Login();
}

private abstract class User
{
    public string FirstName;
    public string LastName;
    public Status Status;
    public int AccountBalance;
    
    public abstract void Login();
}

private class ActiveUser : User
{
    public void Login()
    {
        // Active user logic here
    }
}

private class InactiveUser : User
{
    public void Login()
    {
        // Inactive user logic here
    }
}

private class LockedUser : User
{
    public void Login()
    {
        // Locked user logic here
    }
}

Be Declarative if possible

Take advantage of LINQ in C# and other languages