© 2022 Hashnode
#code-smell-1
TL;DR: Catch your errors. Even the ones you don't expect. Problems Security Error Handling Error Logging Bad UX Experience Solutions Use a top-level handler Avoid languages favoring return co…
On Error resume next was the first thing I learned in my first job TL;DR: Don't avoid exceptions. Handle Them. Problems Fail Fast Principle Violation Solutions Catch the exception and deal with i…
TL;DR: Don't mix indentation styles Problems Readability Code consistency Standards violation Solutions Choose one of them Stick to it Enforce it with code standards tests Share the rules on…
TL;DR: Don't use 'collection' in your name. It is too abstract for concrete concepts. Problems Readability Abstraction Abuse Bad Naming Solutions Rename the collection with a specific name. C…
Code Smell 162 - Too Many Parentheses TL;DR: Use as few parentheses as possible. Problems Readability Syntactic complexity Solutions Remove all not necessary parentheses Context We read code f…
TL;DR: Some ideas on building a friendly intelligent companion. Many people believe that artificial intelligence (AI) is only for big businesses and tech conglomerates. We can use AI can be used for…
TL;DR: If your language has the right tool, your classes should be either abstract or final. Problems Subclassification for Code Reuse Classes with just one concrete subclass Liskov Substitution V…
TL;DR: Don't couple real IDs with invalid ones. In fact: Avoid IDs. Problems Bijection violation You might reach the invalid ID sooner than your think Don't use nulls for invalid IDs either Coupl…
Welcome to the series "Clean Code"; brought to you by "Coding Mantis"! As three is the number of minutes it usually takes to read one of my posts, so is the amount of parameters a method should accept…
TL;DR: Be declarative on mutability. Problems Readability Honor the Bijection mutability. Potential performance and memory issues. Solutions Change the variable to a constant and be clear on i…
