1 views collected around this technical thread.
This article lists nine common TypeScript pitfalls—such as disabling strict mode, misusing the || operator, overusing any, and vague generic names—and explains the correct practices and reasons to adopt them, helping developers write more maintainable and type‑safe code.
The article humorously lists twelve detrimental coding habits—such as over‑splitting microservices, writing excessively long methods, nesting deep conditionals, random variable names, misleading comments, copy‑pasting code, ignoring logs, and reinventing wheels—that reduce code readability and increase maintenance difficulty.
This tongue‑in‑cheek article lists a series of deliberately bad coding practices—ranging from confusing naming conventions and deceptive comments to abusive design choices and omitted testing—intended to illustrate how developers can make their software virtually impossible to maintain.
This tongue‑in‑cheek guide enumerates a series of anti‑patterns—from confusing naming and deceptive comments to absurd design choices and neglect of testing—intended to illustrate how developers can deliberately produce code that is extremely hard to maintain.
The article lists twenty‑one harmful programming habits—such as reinventing wheels, overusing design patterns, skipping testing, ignoring monitoring, and avoiding proper architecture—that can cripple a development team and serve as a warning for engineers seeking better practices.
The article humorously explores nine commonly discouraged programming habits—such as using goto, avoiding documentation, cramming code onto one line, omitting type declarations, and redefining operators—explaining why developers sometimes break rules and how these practices can affect code readability, maintainability, and performance.