New answers tagged

1

I would like to add a different point of view. Lets say we have a product (desktop app, webapp, doesn't matter) that use logs to trace its activity. It does also with errors bc "it's a good product" and errors have been designed with codes (lets say like Oracle does). Such logs/traces were thought to be read by user instead of developers. Product also ...


4

When developers talk about "logs", they're most often referring to plain text files containing information that is meaningless outside the context of the specific code that logged them and has no intended purpose other than troubleshooting that code when something goes wrong. When developers talk about "internationalization", they most often mean "when the ...


0

I would consider avoiding redundant and therefor potentially inconsistent translations and other i18n settings (decimal point, number formats etc.) a best practice here. It depends on your environment/framework which means you have to achieve that, and where you need to add homegrown solutions. Can't say anything about JSE; in Qt I'm using external ...


1

If you have no additional requirements besides what you mentioned in your question, this is perfectly fine. See KISS and YAGNI. You should only consider doing something more complicated right now if you know you're going to need something like internationalization, since deciding on a satisfactory getCorrectStringForCurrentLanguage() mechanism and porting ...


1

AFAIK, this mostly is relevant when you use non-ASCII letter in identifiers (and perhaps comments) in your code. If you discipline yourself to avoid that, e.g. if your code use "English" looking identifiers and keywords and comments, this is much less an issue (and every software developer should be able to read English documentation and code). Then, ...



Top 50 recent answers are included