language agnostic - Best practices for avoiding hardcoded values IRL -


In principle, the hardcoded values ​​in source code should not be beyond 0, 1 and empty string.

In practice, I find it very difficult to avoid all hardcoded values ​​at very rigorous delivery, And I feel a little guilty.

How can you avoid the hard work values ​​over time of tight delivery?

The assumption behind the question seems to be invalid.

For most software, configuration files are very difficult to replace that source code, for widely-installed software, this can easily be a hundred times more difficult to factor: There may be many files hanging on user installation which you have little knowledge and no control.

Librarian functional or algorithm in numeric software is not different from verbatim: it is just source code; it is the responsibility of any software that can be useful to correct those values.

Angered that they should be able to maintain at least: well-named and organized.

It is configurable that it is the last ditch agreement you can be forced if you are in tight schedules.


Comments

Popular posts from this blog

c# - sqlDecimal to decimal clr stored procedure Unable to cast object of type 'System.Data.SqlTypes.SqlDecimal' to type 'System.IConvertible' -

Calling GetGUIThreadInfo from Outlook VBA -

Obfuscating Python code? -