See also the closely related concept of code smells. These are things that aren’t necessarily wrong like anti-patterns are because in certain niche cases or in limited amounts they’re fine, but they’re often an indicator that you’re doing something wrong in your code. As a quick example I looked up some code smells in JS and a couple of the examples were using == instead of === and having deeply nested/indented code (E.G. have if blocks inside of if blocks inside of if blocks inside of a for loop).
Anti-patterns are essentially what ‘not to do’. Heres a good series of Medium articles on it!
Interesting! This feels like it’s going to be something that, once you understand it, you can’t believe you ever programmed without it. Thanks!
See also the closely related concept of code smells. These are things that aren’t necessarily wrong like anti-patterns are because in certain niche cases or in limited amounts they’re fine, but they’re often an indicator that you’re doing something wrong in your code. As a quick example I looked up some code smells in JS and a couple of the examples were using
==instead of===and having deeply nested/indented code (E.G. have if blocks inside of if blocks inside of if blocks inside of a for loop).Haha nice. I’ll keep my nose out for any funky code smells. Thanks!