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…

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

Some objects are always together. Why don’t we split them? — TL;DR: Make cohesive primitive objects travel together Problems Bad Cohesion Duplicated Code Validation Complexity Readability Maintainability Solutions Extract Class Find small objects Context This smell is friends with primitive obsession. If two or more primitive objects are glued together, with business logic repeated and rules between them, we need to find the existing…

Accessing a database in domain objects is a code smell. Doing it in a constructor is a double smell — TL;DR: Constructors should construct (and probably initialize) objects. Problems Coupling Side Effects Solutions Decouple essential business logic from accidental persistence On persistence classes run queries in functions other than constructors/destructors Context On legacy code, the database is not correctly separated from business objects.

Have you ever seen an IEngine in the wild? — TL;DR: Don’t prefix or suffix your classes Problems Readability Bijection Fault Implementative Names Solutions Remove prefixes and suffixes Name your objects after what they do Context Some languages have cultural conventions related to data types, Abstract classes, or Interfaces. These names load our models with cognitive translations hard to follow. We must KISS.

‘Result’ is a very bad generic name. Just Fix it — TL;DR: Use the last call as a semantic guide. Problems Addressed Bad naming on variables Related Code Smells Code Smell 81 — Result result = ???blog.devgenius.io Code Smell 79 — TheResult If a name is already used, we can always prefix it with ‘the’.blog.devgenius.io Steps Name the variable with the same name as the last function call. Sample Code

We learn short circuits in our first programming courses. We need to remember why. — TL;DR: Be lazy when evaluating boolean conditions Problems Side effects Biyection Fault Performance issues Solutions Use a short circuit instead of a complete evaluation Context We learn booleans in our 101 computer courses. Boolean’s truth tables are great for mathematics, but we need to be more intelligent as software engineerings.