News
Code Smell 312 - You Put Multiple Assertions in One Test, Making Failures Hard t...
You put multiple assertions in one test, making failures hard to analyze.
Code Smell 08 - Send Messages Only to Your Direct Acquaintances, Not Their Frien...
Send messages only to your direct acquaintances, not their friends.
Code Smell 311 - Never Store or Compare Plain-text Passwords
When you store or compare passwords as plain-text, you expose users to unnecessary risk.
Code Smell 07 - Avoid Boolean Variables
Avoid Boolean variables, they lead to conditional logic and force you to write Ifs. Create polymorphic states instead
Refactoring 035 - Use Separate Exception Hierarchies for Business and Technical...
Use separate exception hierarchies for business and technical errors.
Refactoring 034 - Wrapping Messy Parameters Into a Single Meaningful Entity
Wrap messy parameters into a single meaningful entity.
Code Smell 309 - Query Parameter API Versioning
Maintain clear version documentation, test versions thoroughly, and deprecate old versions gradually.This practice will ensure th...
Code Smell 05 - Comment Abusers
Leave comments just for important design decisions. Don't explain the obvious.
Refactoring 033 - Removing Redundant or Unused Annotations
Make your code simpler and more maintainable by removing redundant or unused annotations.
Code Smell 04 - Stop Abusing Strings—Use Real Objects Instead
Use real abstractions and real objects instead of accidental string manipulation.
Refactoring 032 - Apply Consistent Style Rules
When machines generate large amounts of code, you need to apply one consistent style to all files.
Code Smell 03: Functions Are Too Long - Here's How to Fix That
Refactor and extract functions longer than 5 lines. Here's how.
