Re: Data oriented programming

I think a great way to synthesize agile vs. planning is that if you are going to plan, you should also plan on validating that plan. And if you are going to be agile, realize that the fundamental property of agile is a learning process. Which means experimentation and reflection, not just experimentation.

MSN
-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of Richard
Sent: Thursday, September 30, 2010 2:07 PM
To: [email protected]
Subject: Re: [Sweng-Gamedev] Data oriented programming


In article <[email protected]>,
    Fabian Giesen <[email protected]> writes:

> > Not that I disagree, but if you're in trouble isn't it best to know as
> > soon as possible?  That's all I'm asserting.
> 
> Yes, it is best to know as soon as possible, and integration testing is 
> most emphatically not "as soon as possible" for architectural decisions. 
> Back-of-the-envelope calculations during the design stage are.

... but of course those calculations are done by error-prone humans
and can be done wrong.

And just because you decide on an architecture in the beginning
doesn't mean that other people on your team are adding things
consistent with that architecture.

There's nothing wrong with planning things up front.

CI tests ensure that reality is consistent with that plan.

Designs are propositions and postulates, not measured data.
-- 
"The Direct3D Graphics Pipeline" -- DirectX 9 draft available for download
 <http://legalizeadulthood.wordpress.com/the-direct3d-graphics-pipeline/>

      Legalize Adulthood! <http://legalizeadulthood.wordpress.com>
_______________________________________________
Sweng-Gamedev mailing list
[email protected]
http://lists.midnightryder.com/listinfo.cgi/sweng-gamedev-midnightryder.com
_______________________________________________
Sweng-Gamedev mailing list
[email protected]
http://lists.midnightryder.com/listinfo.cgi/sweng-gamedev-midnightryder.com