This general design principle does not mean to never change anything, but to consciously create a paradigm where the same things have the same names and are accessed in the same way as much as possible. Read the rest of this entry »
Tag Archives: code style
This is the first of a series of posts, I want to go over some of the groundwork of what it takes to make exceptions localizable into other languages. Nothing new here, but just want to explain clearly the requirements of a localizable exception messages.
Still reviewing that code base and finding more bad patterns for use of constants, this time for error messages. This is another “don’t do this” post. Read the rest of this entry »
Software will always increase in amount and size, and that includes not only things that are needed, but unneeded things as well. Unless you fight diligently against it, code will tend to get more and more cluttered. Read the rest of this entry »
A “best practice” is a heuristic which is used to guide early stages of a project, in order to set some patterns. When should you use them? More important: when are you justified in ignoring a best practice? Read the rest of this entry »