Re: Data oriented programming

Fabian 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.

Then Gregory wrote:
> Which can easily lead to "analysis paralysis"...

To which I replied:
> So you are recommending that you shouldn't think about the performance
> impact of your code before you write it?

And the Gregory replied:
> I don't see how you could possibly have read that into my comments.

Your terse comment lead me to think that you didn't like the idea of
considering performance before implementation as it could lead to analysis
paralysis. If you were just making a statement about analysis paralysis
then, I agree, yes it can. But the fear of analysis paralysis (analysis
paralysis paralysis?) is more likely to have a detrimental long term effect
on your code base than the former.


-Tony




On 7 October 2010 07:21, Gregory Junker <[email protected]> wrote:

> Sorry, thanks to Outlook assuming everyone wants to write HTML in their
> emails, this isn't clear; edited for who said what.
>
> > Tony said:
> > So you are recommending that you shouldn't think about the performance
> > impact of your code before you write it?
> >
>
> I said:
>
> I don't see how you could possibly have read that into my comments.
>
> 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