Essay/Software 2008.02.19 00:26
[[ blog 이사 과정에서 정확한 posting날짜가 분실됨. 년도와 분기 정도는 맞지 않을까? ]]
Output files should be separated from input files. Usually, 'clean' option is supported to delete auto-generated-output-files. But, separating outputs at directory level is better - for example, 'out' directory is root directory for output.
This is very basic and fundamental. But, this also easily ignored.
Supporting 'clean' option is good. But, cleaning output files those are scattered over several different places, is difficult to maintain. And, in this case, to find some necessary output files is also difficult.
On the environment that output files are separated at directory level, programmer can tell easily that which is input and which is output. This means, he/she can know which are necessary files to build software without further efforts - easy to read software.
|[Prog] Trade offs (0)||2008.05.12|
|[Prog] Avoid prematured exception handling... (0)||2008.04.27|
|[Prog] Outputs should be separated from inputs at directory level. (0)||2008.02.19|
|[Dev] Let's make schedule-history-table! (0)||2007.11.25|
|[Dev] Required comments in change list. (0)||2007.08.11|
|[Essay] Timezone이 다른 지역의 사람들과 같이 일할때... 이런 방법은 어떨까?? (0)||2007.07.10|