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

You should not define too much behavior together — TL;DR: Split your interfaces Problems Interface Segregation Principle Violation Coupling Solutions Split the interface Context The term "Fat Interface" emphasizes that the interface is overloaded with methods, including those that may not be necessary or used by all clients. The interface violates the principle of segregating interfaces into smaller, more focused contracts.

Metaprogramming is always a problem — TL;DR: Don't allow remote code execution Problems Security Solutions Validate and sanitize input Avoid executing code. Input only data Apply sandboxing or isolation Context Deserializing objects from an untrusted source is indeed a security-sensitive operation. Suppose you have a web application that accepts serialized objects as input from user-submitted data, such as in…

Two arguments of the same type. Two equal names — TL;DR: Turn on Strict Checks Problems Unexpected errors Ambiguity The Least Surprise Principle violation Portability Solutions Enable strict mode Use role-naming arguments Context Most compilers forbid duplicate parameters since they are a common mistake in a large parameters list Sample Code Wrong function addNumbers(a, b, a) { console.log(a …

You can prevent undefined — TL;DR: Declare your variables and watch the scope Problems Readability Least Surprise Principle violation Variable Shadowing Solutions Be explicit on declarations Use ‘const’ declaration when possible. Declare variables at the beginning of the scope. Use strict mode Context Hoisting allows variable declarations to be moved to the top of their containing scope during…

Your code is not safer using this operator — TL;DR: Don't propagate nulls. Problems NULL propagation Harder to read code Hacky code Solutions Remove the nulls. If you can't remove it, deal explicitly with them. Context The Elvis operator is also known as the null-coalescing operator or the null-safe operator. It is a shorthand operator used in some programming languages to simplify…