> <i>Hard-coding data.</i><p>I’m not convinced.
Is the constant Pi not data? A multi-byte file magic? A constant matrix used for rotation?<p>> <i>Put strings (like labels, messages, hints …etc ) directly in the code instead of externalizing them.</i><p>Many enterprise software projects are custom-built for a handful of users and don’t need externalization.
Besides, log messages.<p>> <i>Not using meaningful names for variables.</i><p>Strongly agree.<p>> <i>Using name instead of verb in method/function declaration.</i><p>What about getter methods? In some languages, `get` or `is` prefixes are not idiomatic.<p>> <i>Rolling his own security</i><p>What is that even supposed to mean? Of course we roll our own security. It needs to be baked into the product from the design phase on.<p>What the author probably meant was: security algorithms. Maybe reflect on why they seem to assume all programmers are men.<p>> <i>Jump staging right to the production.</i><p>What about ad-hoc debug helpers that sometimes have to be inserted while debugging in production?<p>> <i>No comment !</i><p>Some pieces of code just don’t need comments.