Re: Data oriented programming

So you are recommending that you shouldn't think about the performance
impact of your code before you write it?

I think you should. If you are working on code which is likely to have a
performance impact on a system, then you should think carefully about the
layout of data and code. Smart decisions at the start will save you a lot of
time in the long run. I've worked on systems that are incredibly difficult
to optimise due to uniformly slow code where a week spent fiddling around
during the design of the system would have saved months down the track.

-Tony

On 6 October 2010 14:18, Gregory Junker <[email protected]> wrote:

> >
> > I didn't mean to suggest that you shouldn't test performance during
> > testing, just that it shouldn't be your "first line of defense".
> > Obviously you can't fix problems before you notice them, but a lot of
> > these problems are entirely avoidable if you think things through early
> > enough.
>
> Which can easily lead to "analysis paralysis"...
>
> Greg
>
> _______________________________________________
> 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