↓ Ir para o conteúdo principal

← todas as notas

📎 Webclip

9 Anti-Patterns Every Programmer Should Be Aware Of

The article argues that programmers should cultivate self-criticism to spot unproductive patterns in design, code, process, and behavior. It treats anti-patterns as guidelines rather than fixed rules and warns against dogmatic thinking. Each section explains what the anti-pattern is, why it is harmful, how to avoid it, and when the boundary cases are hardest to judge.

Reading notes
#

  • Premature optimization means trying to optimize before there is enough data to know where the bottleneck is, which usually adds complexity and bugs for little gain.
  • Bikeshedding is spending too much time debating trivial or subjective choices, such as UI colors or indentation style.
  • Analysis paralysis happens when over-analysis delays or blocks action, and the article recommends iterating so decisions can be based on new feedback.
  • God classes accumulate many dependencies and responsibilities, making them hard to test, debug, document, and maintain.
  • Fear of adding classes can keep designs too tangled, even when breaking a large class into smaller ones would simplify the system.
  • The inner-platform effect appears when software reimplements features already provided by the platform or language, often poorly.
  • Magic numbers and strings hide meaning in unnamed literals, which makes code harder to understand and refactor.
  • Management by numbers uses metrics too rigidly for decisions, even when the measurements no longer match reality or become easy to game.
  • Useless classes add abstraction without responsibility, acting as pass-through wrappers that increase confusion and maintenance work.