Christoph Hormann wrote:
> Andrew Clinton wrote:
>> So, when discussions begin for POV-Ray 4.0, will the Team provide an open
>> forum for user suggestions?  My vote is for "povray.wishlist".  As a
>> programmer, I'm also wondering how you really keep "requirements" and
>> "design" seperate.  A discussion of requirements necessitates some degree
>> of discussion of feasibility,
> 
> No.  As an engineer i can tell you that when planning a new design you
> start with the requirements alone.  Limiting the requirements from the
> beginning to only require what is feasible will result in no innovation
> at all (and i am quite sure this applies for program design as well).
> So what you write here to me indicates that you have no idea what
> formulating the requirements actually means.
> 
I completely agree with you that this approach ultimatively yields to 
the best solution. First one should just think _what_ one would like to 
be able to do with it - and not _how_. 

The only problem is that this way it tends to take ages until the product 
is in production state. And then the problem is also to not loose interest 
in it in between. 

Wolfgang

Post a reply to this message