A seemingly harmless hack to resolve an issue can quickly set a precedent in your codebase, says Kealan Parr. It can be copied across multiple places and turn into an anti-pattern.
“Anti-patterns are considered bad software design and are usually ineffective or obscure fixes. They generally also add "technical debt" — which is code you have to come back and fix properly later,” Parr says.
This article outlines six common anti-patterns to understand and avoid, including spaghetti code, dead code, and the dreaded boat anchor.
Read more at freeCodeCamp.
Comments