the capacity to code
category: general [glöplog]
I'm feeling a bit under today... I've been reading and re-reading a tutorial on a specific effect, and I just cant seem to get it. The tutorial says its a simple effect, wich makes it all the more frustrating. I'm beginning to wonder if this is a sign that I lack the capacity for coding.
I want to code. It fascinates me. I enjoy doing it (what little I can do). But some of the simple things are just beyond me, wich makes me wonder if I should just stick to Quake, and let someone else handle the code.
My question to you is, how do I know if I lack the capacity? How do I know if i'm stepping out of the relm of my natural ability, and wasting my time doing so?
I want to code, but I dont want to waste my time on trying to learn concepts I will never grasp.
Any advice would be most appreciated. thnx :)
I want to code. It fascinates me. I enjoy doing it (what little I can do). But some of the simple things are just beyond me, wich makes me wonder if I should just stick to Quake, and let someone else handle the code.
My question to you is, how do I know if I lack the capacity? How do I know if i'm stepping out of the relm of my natural ability, and wasting my time doing so?
I want to code, but I dont want to waste my time on trying to learn concepts I will never grasp.
Any advice would be most appreciated. thnx :)
i'm reading this book now.
just so you know.
just so you know.
looks nice
creating quality demos is 10% coding/music/gfx skill and 90% perseverance.
when you start spending more time ranting on how you dont get it instead of trying to get it and experimenting with it. thats when you know.
all look the same. btw, it was not related to your question.
ok here are my opinions (beware, they usually suck):
try to code your own "effects". make lots of senseless tiny stuff. (don't release them anywhere, especially here.) you'll eventually re-invent some well known effects.
nothing is simpler than a starfield, first do it.
probable. who gives a fuck? you shouldn't also.
you shouldn't.
people waste "years" for learning, be a man and stick to it.
ok here are my opinions (beware, they usually suck):
Quote:
reading and re-reading a tutorial on a specific effect
try to code your own "effects". make lots of senseless tiny stuff. (don't release them anywhere, especially here.) you'll eventually re-invent some well known effects.
Quote:
its a simple effect
nothing is simpler than a starfield, first do it.
Quote:
I lack the capacity for coding
probable. who gives a fuck? you shouldn't also.
Quote:
I should just stick to Quake
you shouldn't.
Quote:
waste my time on trying to learn concepts
people waste "years" for learning, be a man and stick to it.
I'm not really that into ranting about how people should learn their thing but let's get the fact straight. Looking into your previous work you should first learn the programming language and then proceed to graphics programming and not the other way around. Yes, it's probably frustrating to code some dull console applications but that is life so get used to it :P
Maybe you are just a victim of the http://c2.com/cgi-bin/wiki?YouCantLearnSomethingUntilYouAlreadyAlmostKnowIt
You don't lack the capacity. Your brain is most probably just untrained for that kind of stuff. Practice more!
ITS AMAZING TO SEE ALL THEESE LAMERS HERE COMMENTING HOW EVERYBODY CAN LEARN TO CODE LIKE ME. SERIOSLY: YOU CANNOT!
more practice more confused
let parse43 code ;) hehehe.. no. keep on.. i guess you learn someday but you will be never as good as stefan of deus ex machine
parse43 is potential young to try codes i think, as gfx boy becoming code-guy, that's brilliant!
can we see said code?
xteraco: we all have limitations, but they seem to be moving all the time together with our skills. progressing as a coder is much about that very thing; moving your boundaries.
havoc: how true :|
