Why the first instruction we learn to program should be the last to use. Nobody uses GOTO instruction anymore and few programming languages still support it. We have matured and confirmed spaghetti code is unmaintainable and error prone. Structured Programming solved that problem years ago. We got rid of the…

Incomplete objects cause lots of issues. Problems Mutability Incomplete objects Concurrency inconsistencies between creation and essence setting. Setters Nude Models — Part I : Setters Ye olde Reliable Data Structures and Their Controversial (Write) Access.medium.com Solutions Pass the object’s essence on creation The evil powers of mutants To mutate is to evolve. It was proposed by Sir Charles Darwin and we use it in the software industry. But something is…codeburst.io

The code smells bad. Let’s see how to change the aromas. — TL;DR: A Compilation of bad smells in code. In this series, we will see several symptoms and situations that make us doubt the quality of our developments. We will present possible solutions. Most of these smells are just clues of something that might be wrong. They are not rigid rules. Code Smells Code Smell 01 — Anemic Models Your objects are a bunch of public attributes without behavior.medium.com

Your objects are a bunch of public attributes without behavior. — Protocol is empty (with setters/getters). If we ask a domain expert to describe an entity he/she would hardly tell it is ‘a bunch of attributes’. Problems No Encapsulation. No mapping to real world entities. Duplicate Code Coupling Solutions 1) Find Responsibilities. 2) Protect your attributes. 3) Hide implementations. 4) Delegate Examples

Pass by copy, pass by reference. which is better? — TL;DR: Beware of passing arguments by reference Problems Unexpected Results Side Effects Readability Broken Encapsulation Solutions Pass arguments by copying even large objects. Don’t make premature optimizations. Declare variables as constants Refactor the code Make objects immutable to avoid accidental changes 5 Use Pure Functions Context A call-by-reference language like C# or PHP…

You use nice words to excuse bad code — TL;DR: Don't excuse bad code. Write a clean one! Problems Readability Solutions Rewrite the code and delete the comment Context The term comes from Martin Fowler's book "Refactoring: Improving the Design of Existing Code" Sample Code Wrong # This is a function that adds two numbers def s(a, b): # Now you are going…

Software evolves, and so does culture. — TL;DR: Avoid old terms like whitelists, blacklists, master, etc. Problems Racial Connotations Exclusionary Language Diverse Perspectives Solutions Use alternative terminology Context Language evolves, and technical terms should follow it. You can change racial names with alternative terminology: Allowlist: Replace “whitelist” with “allowlist.” This term maintains the intended meaning without racial connotations.

Don't abuse this fancy operator — TL;DR: Use comma operator just for loops Problems Readability Hidden Defects Solutions Avoid operator usage Prefer foreach operator Break the sentences Context In JavaScript, the comma operator allows you to evaluate multiple expressions sequentially and return the value of the last expression. It's denoted by a comma and separates multiple expressions within a…

You abuse cases in switches and make subtle mistakes — TL;DR: Cases are GOTOs, but you might be missing them Problems Hidden defects Readability Solutions Add the missing break Convert the switch into a polymorphic hierarchy Remove the default switch Context In a switch statement, when a match is found in a particular case, the code execution will start from that case and…