neoe's config-driven development

I began to write a new program.
I write in different ways each time.
this time I begin with a rich config file.
I realized I applied a new approach.
It can be called config-driven development, just the name, you know things are great different having the same name.

pros:
features are determined early.
the input data(const, configurable parameters, etc...) is determined early.
the config file is written in neoe-way(called "smart simple") on contrary of "xml verbose dumb way".
if config file is good enough, it acts like a script language.

cons:
more efforts on code.