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

Don't Repeat Yourself. Don't Repeat Yourself — TL;DR: You can find missing abstractions by looking at repeated code Problems DRY principle violation Maintainability Ripple Effect Solutions Create the repeated code Introduce an abstraction Replace the references and point to the new abstraction Remove the duplication Context Repeated code is a symptom of missing abstractions. This is natural in the learning…

Converting your anemic dictionaries is easy — TL;DR: Convert your key/value into full behavioral objects Problems Addressed Associative arrays Fail Fast principle violation Bijection Fault Hard to find method references Related Code Smells Code Smell 27 — Associative Arrays [Key, values], magic, fast, malleable and error prune.blog.devgenius.io Context You have anemic associative arrays that hold unstructured data and you want to have richer objects with stricter controls (possibly including type checking in static typed languages)

Your code is dead and alive — TL;DR: Look carefully for race conditions Problems Principle of Least Surprise violation Race Conditions Solutions Avoid race conditions Avoid global variables Use proper synchronization Context Schrödinger code is code that can be in two different states at the same time, but the state of the code is not determined until it is executed. …

You overcomplicate your code — TL;DR: Avoid Accidental complexity and bureaucracy Problems Accidental Complexity Readability Bijection Fault Solutions Asign the responsibilities to real-world objects using the MAPPER Context A "red tape" code smell could relate to unnecessary complexity, bureaucracy, or excessive configuration that makes the codebase harder to understand or maintain. Sample Code Wrong

More than one class is a mess — TL;DR: Follow the separation of concerns principle and file organization Problems Code Organization Coupling Autoloading problems Debugging Version control and merge conflicts Solutions Declare a single class per file Use name scoping Context In languages that declare classes using a file system, having one class per file is generally considered a best practice. …