Programming-Basic

Detailed Refactoring Series: Part 1: Refactoring - Part 1 (Principle, What It Is & Is Not, Identify the Smells First) Refactoring Book Book introduction Martin Fowler’s “Refactoring: Improving the Design of Existing Code” is a classic book that teaches developers how to improve the structure of existing code without changing what it does. Refactoring makes code easier to read, maintain and expand, helping teams write better software over time. ...

Detailed Clean Code Series: Part 1: Writing Clean Code - Part 1 (Conceptually Clean and Bad Code) Clean Code Book (Photo Credit: SoBrief) Book introduction “Clean Code: A Handbook of Agile Software Craftsmanship” by Robert C. Martin (popularly known as Uncle Bob) is one of the most influential books in software engineering. It focuses on the principles, patterns, and best practices for writing clean, maintainable, and efficient code. ...

Other Parts of This Series: Part 3: Writing Clean Code - Part 3 (Formatting, Class & Object, Miscellaneous) Code Smells (Photo Credit: Axify) Story Our prophet Hazrat Muhammad Sallallahu Alayhi Sallam advised us that “Always try to avoid the acts of sin/bad things because if someone can avoid the bad work, he/she will start doing good work automatically.” This is true for both our real life and writing code. If we can avoid the code smell or bad code, then our code will automatically be good and clean. So identifying the code smell is important. ...

Other Parts of This Series: Part 2: Writing Clean Code - Part 2 (Name, Function, Comment) Part 4: Writing Clean Code - Part 4 (Identify Code Smells/Bad Code) Clean Code - Formatting, Class & Object, Miscellaneous (Photo Credit: Sotatek) Remember 2 things: The only measurement of your code is WTFs / Minute. That is what the readers feel when reviewing code. Linux Torvalds, the creator of the Linux operating system, says, “Talk is cheap; show me the code.” So if we connect the above 2 points, then we can easily understand that our code should be talkable and self-describing because when anyone reviews/reads our code, they should feel well and comfortable enough. ...

Other Parts of This Series: Part 1: Writing Clean Code - Part 1 (Conceptually Clean and Bad Code) Part 3: Writing Clean Code - Part 3 (Formatting, Class & Object, Miscellaneous) Clean Code - Name, Function, Comment (Photo Credit: Prezi) Remember 2 things: The only measurement of your code is WTFs / Minute. That is what the readers feel when reviewing code. Linux Torvalds, the creator of the Linux operating system, says, “Talk is cheap; show me the code.” So if we connect the above 2 points, then we can easily understand that our code should be talkable and self-describing because when anyone reviews/reads our code, they should feel well and comfortable enough. ...