You are getting me quite wrong here, I want things "that definitely works" and that work without crashing, that's why I want to know EXACTLY what I am doing and why I am doing it not dealing with stuff that hides from me what I am doing even if this "simplifies" in the beginning at least a bit.Orangy Tang wrote:It shouldn't surprise me that everyone's background affects how they approach programming to a huge extent, but it still does. For me that mostly means trying to write fully functional, polished and complete games as a one man show in my spare time while still programming 'proper' games full time at work. So that means using any means necessary to write code quicker. And by extension that means writing less code where possible, and writing code to minimise debugging time (both now and to maintain it). I like simple, straightforward, elegant code that expresses the algorithm and logic at work rather than code that's 10% algorithm and 90% dicking around with stuff the language forces you to care about.
Which is why when I see posts like Gile's obsessing over every little byte and cache line and cycle I just want to grab him and shake him and say "What are you doing man? You're wasting your precious coding time obsessing over tedious implementation details because you're control freaking out over every last byte!".
As a lone wolf programmer, time is my most precious resource, and by comparison cycles and bytes are cheap and plentiful. Computers should help me get to where I want to be faster, not drag me down with their discipline and bondage they need to be kept happy.
Oh, and languages, roughly in order: BASIC, C, x86 ASM, Java, Prolog, C++, Python, GLSL, C#, Javascript, Ruby, 6800 asm, Lua.
"If I don't know what I am doing I can't fix it".
Trust me I believe it too in KISS ( Keep It Simple and Stupid ) or better to say "Keep It As Simple As Possible".
When you do certain stuff on not-so-powerful-machines you will find out that bytes are not so cheap nor plentful nor cycles at all, I still remember how much we were "on despair lane" when we did try the first time porting the Neon engine on the iPad and everything was crawling like shit and we did not understand what was going wrong.
Ask Yak about the story of "the blue sky on five a day" another example where "the most elegant and straightforward solution was the worst" - despite looking really the simplest one.
- it must not crash
- it must run smooth
- 60 fps or die
- I must like it
And also .. "if you are doing something that is not what you really want to do, then you should not do it".
I stopped doing some jobs because I really could not stand any more doing things I did not want to do .. so .. I mean "yes BUT" .. if you can't do what you really like to do what's the point then





