Maximiliano Contieri

3 weeks ago | dev.to | Maxi Contieri |Maximiliano Contieri

When your API says "Everything is fine!" but returns errorsTL;DR: Returning a successful HTTP status when the actual result contains an error confuses the API consumers.

3 weeks ago | hackernoon.com | Maximiliano Contieri

Transform optional attributes into empty collections for cleaner, safer, and polymorphic code, banishing the billion-dollar mistakeTL;DR: Replace nullable optional attributes with empty collections to eliminate null checks and leverage polymorphism.

3 weeks ago | dev.to | Maxi Contieri |Maximiliano Contieri

Transform optional attributes into empty collections for cleaner, safer, and polymorphic code, banishing the billion-dollar mistakeTL;DR: Replace nullable optional attributes with empty collections to eliminate null checks and leverage polymorphism.

1 month ago | hackernoon.com | Maximiliano Contieri

Passing databases creates accidental coupling and breaks business encapsulation. TL;DR: Don't mix data access concerns with essential business behavior. Problems ๐Ÿ˜”Tight CouplingMixed responsibilitiesBijection violationTestabilityBusiness logic pollutionSeparation of concerns violationBlurred LayersSingle Responsibility Principle violationSolutions ๐Ÿ˜ƒUse dependency injectionDon't use the Repository Pattern.

1 month ago | maxicontieri.substack.com | Maximiliano Contieri

TL;DR: Don't mix data access concerns with essential business behavior. Tight CouplingMixed responsibilitiesBijection violationTestabilityBusiness logic pollutionSeparation of concerns violationBlurred LayersSingle Responsibility Principle violationUse dependency injectionDon't use the Repository Pattern.