9 Anti-Patterns Every Programmer Should Be Aware Of
Published
•1 min readM
Hands-on technology leader with 10+ years building scalable, mission-critical systems at Goldman Sachs, Brevan Howard and fast-growing fintechs. Expert in cloud-native architectures, distributed data pipelines and high-throughput systems; experienced in migrating legacy platforms and designing AI-enabled services. Proven track record delivering reliable platforms that process millions of transactions daily.
- Premature Optimization: Do not optimize too early before you know bottlenecks and problems in the live environment.
- Bikeshedding: Do not spend time on minor topics
- Analysis Paralysis: Do not analysis too much.
- God Class: Avoid big classes that control many other classes.
- Fear of Adding Classes: Add new classes if necessary and do not fear about the complexity.
- Inner-platform Effect: Try to use available features of your OS instead of re-writing them in your programming language.
- Magic Numbers and Strings: Avoid magic and undocumented numbers in your code.
- Management by Numbers: Do not rely too much on numbers like LoC.
- Useless (Poltergeist) Classes: If class is not doing anything valuable, remove it.