2 ms·
I mostly agree with exception of: it heavily depends on where you work. The exact logging configuration example is a prime example of what an ISV customer would
by zamalek 11y ago
I mostly agree with exception of: it heavily depends on where you work. The exact logging configuration example is a prime example of what an ISV customer would want to change - many of our customers (and QA) go as far as writing their own adapters so they need to be able to completely customize the configuration.
You have to draw the line somewhere, though. I tend to err on the side of "unconfigurable" until a request is made to make something configurable. E.g. Someone had the smart idea of having all our logging messages in a config file all the years back when the logging component was written, which is an incredibly frustrating anti-pattern. That was never needed and the messages should have been stored elsewhere.
- droffel 11y ago"Someone had the smart idea of having all our logging messages in a config file all the years back when the logging component was written, which is an incredibly frustrating anti-pattern. That was never needed and the messages should have been stored elsewhere." The company that i'm currently working for uses this pattern in their software, so they can properly internationalize the messages. Unless I'm misunderstanding the context of your comment, storing the messages in a configuration file can potentially be a logical design decision.
- zamalek 11y ago> The company that i'm currently working for uses this pattern in their software, so they can properly internationalize the messages. It's .Net so the "correct" way to do that would be to use .resx, which have built-in architecture for localized messages (even though they are still XML files). There's more reasons for me disagreeing strongly with the specific implementation, but it's a tiny part of the stack that rarely gets used; I'm making a mountain out of a molehill. It was just one example that I had on-hand.