Re: Data oriented programming

Personally I think that it's difficult to find a balance between writing
code, knowing performances from both a large and small scale, think what you
have NOT to do...it's a matter of experience and open mind/study.
I don't like the "coding" paralysis that many software engineering have (me
included until some time ago), because having "fear" of writing code because
it's not too much clean/with good performance can lead to writing nothing
(that is far worst).
Also I don't like the pattern mentality, because many times it's more a
matter of context and circumstances/experience in the code you write.
So for me, I started giving me a "decision time", after which I'll start
writing code. Then I'm writing down what can be improved, both from the
performances that from the interface design, and features: in that way I'm
finding a balance between cowboy coding and code paralysis.

Just my 50c, even if I'm not experienced as you, I wanted only to hear your
experiences with Data Oriented Programming.

By the way, thanks anybody for the replies!

    Gabriel Sassone

_______________________________________________
Sweng-Gamedev mailing list
[email protected]
http://lists.midnightryder.com/listinfo.cgi/sweng-gamedev-midnightryder.com