Maximiliano Contieri

Published in Dev Genius

·Pinned

How to Develop a Wordle Game using TDD in 25 Minutes

Developing a complete Wordle Game is very easy with TDD — Everybody is playing Wordle these days… And I love TDD. TDD Conference 2021 — All Talks First International Test Driven Development took place on July 10th.blog.devgenius.io So, let’s get moving… TL;DR: With just a few steps we can build a robust Wordle. Defining a word The minimum information amount in Wordle is a word. We can argue that letter is smaller, but we think all needed letter protocol is…

Test Driven Development

6 min read

How to Develop a Wordle Game using TDD in 25 Minutes

Test Driven Development

6 min read

Published in Dev Genius

·Pinned

How to Get Rid of Annoying IFs Forever

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…

6 min read

6 min read

Published in Dev Genius

·Pinned

Code Smell 13 — Empty Constructors

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

Code Smells

2 min read

Code Smells

2 min read

Published in Dev Genius

·Pinned

How to Find the Stinky Parts of Your Code

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

Code Smells

15 min read

How to Find the Stinky parts of your Code

Code Smells

15 min read

Published in Dev Genius

·Pinned

Code Smell 01 — Anemic Models

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

Code Smells

1 min read

Code Smells

1 min read

Published in Level Up Coding

·4 days ago

Code Smell 201 - Nested Ternaries

Arrow Code, Nested Conditions, switches, else, and many more — TL;DR: Don't use nested IFs or nested ternaries Problems Readability Default Case Solutions Rewrite the code as an IF condition with an early return Context Nesting is always a problem with complexity. We can fix it with polymorphism or early returns Sample Code Wrong const getUnits = secs => ( secs <= 60…

Code Smells

2 min read

Code Smells

2 min read

Published in Level Up Coding

·Mar 9

Code Smell 200 — Poltergeist

An object that appears and disappears mysteriously — TL;DR: Add the necessary indirection layers, but no more. Problems Accidental complexity Readability YAGNI violation Solutions Remove the intermediate object Context A poltergeist (or gypsy wagon) is a short-lived object used to perform initialization or to invoke methods in another, more permanent class. An object is responsible for many small tasks, resulting in…

Clean Code

2 min read

Clean Code

2 min read

Published in Level Up Coding

·Mar 6

Code Smell 199 — Gratuitous Booleans

A code that either returns or no returns at all — TL;DR: Check carefully your boolean expressions Problems Readability Possible Defects Solutions Refactor and remove obsolete code Context When a function is designed to return an invariant value, it may be poor design, but it shouldn’t adversely affect the outcome of your program. …

Code Smells

2 min read

Code Smells

2 min read

Published in Level Up Coding

·Mar 3

Code Smell 198 — Hidden Assumptions

Software is about contracts and ambiguous contracts are a nightmare — TL;DR: Keep your code explicit Problems Coupling Fail Fast Principle violation Bijection Fault Solutions Be declarative and explicit Don’t oversimplify Context Hidden assumptions are underlying beliefs or expectations not explicitly stated in the code. They are still present and can impact the behavior of the software. Various reasons can give rise to assumptions…

Clean Code

2 min read

Clean Code

2 min read

Published in Level Up Coding

·Feb 23

Code Smell 197 - Gratuitous Context

This is a nice way to mark 'your' classes and objects — TL;DR: Don’t prefix or suffix your names with irrelevant information Problems Lack of Polymorphism Bad Naming Bijection violation with names Solutions Remove this context from your names Context In software development, gratuitous context refers to the unnecessary inclusion of additional information or data in code or user interfaces that do not contribute to…

Clean Code

2 min read

Clean Code

2 min read