✨ How to Write Clean Code – It’s More Than Just Making It Work

"The difference between a good programmer and an average one isn’t whether their code runs… it’s whether their code makes sense." – Someone wise

---

🎯 First of All, Why Even Care About Writing Clean Code?

Let’s be honest. Most of us, when writing code, just want it to work. But working code isn’t enough. Code gets read, maintained, and modified—by others or by you after a few weeks.

Studies show that developers spend over 70% of their time reading code. So if the code’s messy? That’s hours wasted, bugs introduced, and a lot of swearing from teammates.

---

💡 1. Use Clear, Meaningful Names

Variable and function names should explain what they are, not confuse the reader.

// ❌ Bad:
int x = 7;
if (x > 5) doSomething();

// ✅ Good:
int minimumAge = 7;
if (userAge > minimumAge) allowAccess();

• Let the name tell the story.
• Don’t force readers to look elsewhere to understand a variable.
• Avoid cryptic abbreviations—unless universally known.

---

🔧 2. One Function = One Purpose

If your function does three different things, it’s not a function—it’s a soap opera. Clean functions do one thing well.

// ❌ Bad:
void processUser() {
    getUserInput();
    calculateSalary();
    sendEmail();
}

// ✅ Good:
void getUserInput();
void calculateSalary();
void sendEmail();

---

🧼 3. Delete Dead Code

Any line of unused code? Delete it. It’s noise. Version control exists for a reason.

“Dead code is like an empty trash can in your kitchen—useless, but annoying.”

---

📖 4. Code Should Read Like a Story

Read your code like a sentence. If it feels like a riddle, rewrite it.

// ❌ Unclear order:
saveUser();
getData();
logResult();

// ✅ Clear flow:
getData();
saveUser();
logResult();

---

🧠 5. Don’t Repeat Yourself (DRY)

If you’re writing the same code multiple times—stop. Extract it into a function.

// ❌ Bad:
cout << "Welcome " << name << endl;

// ✅ Good:
void printWelcome(string name) {
    cout << "Welcome " << name << endl;
}

---

💬 6. Use Comments Wisely

Comments should explain the why, not the what. Use them only when necessary.

// ❌ Redundant:
int a = 5; // number of students

// ✅ Better:
int studentCount = 5;

---

🎨 7. Make It Look Nice

Use whitespace and consistent formatting. Cramped code is hard to read.

void getUserInput() {
    // ...
}

void processData() {
    // ...
}

void displayResult() {
    // ...
}

---

📘 The Best Resource Out There?

Clean Code by Robert C. Martin (Uncle Bob)

"Leave the campground cleaner than you found it."

---

✅ Final Summary

Tip	Key Idea
Clear names	Code should explain itself
One purpose	Functions shouldn’t multitask
Kill dead code	Less noise = more clarity
Logical flow	Let code tell a story
Don’t repeat	Repetition = problems later
Smart comments	Only when needed
Style matters	Formatting is a form of respect

---

🎁 In the End...

Clean code is about respect:

• Respect for the next developer (even if that’s you)
• Respect for your team
• Respect for the craft of programming itself

Start now. Shift your mindset from “just make it run” to “make it beautiful and maintainable.”