Maximiliano Contieri

1 week 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 week 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.

3 weeks ago | maxicontieri.substack.com | Maximiliano Contieri

TL;DR: Replace sequential IDs in your models with UUIDs to prevent IDOR vulnerabilities and discourage scraping. IDOR VulnerabilityPredictable URLsData and Screen Scraping RiskTight Coupling to accidental Database IdentifiersExposure of Internal StructureCode Smell 120 - Sequential IDsCode Smell 160 - Invalid Id = 9999Thanks for reading Clean Code Cookbook! Subscribe for free to receive new posts and support my work.

3 weeks ago | maxicontieri.substack.com | Maximiliano Contieri

TL;DR: Avoid hallucinated or fake packages that can compromise security and stability.

4 weeks ago | hackernoon.com | Maximiliano Contieri

When your test setup is bigger than the actual testTL;DR: Bloated setup that's only partially used makes your tests more coupled and harder to understand.