Hmm....why don't you try that out and see what you get.
Hmm....why don't you try that out and see what you get.
Originally Posted by anduril462
Warning: Some or all of my posted code may be non-standard and as such should not be used and in no case looked at.
I did and it works perfectly. How'd you decipher it so fast?
Quzah and I phoned him and told him what to post in a conference callI did and it works perfectly. How'd you decipher it so fast?
Very efficient. :P haha thanks a lot for the help guys. Hopefully after a little more experience I can help future noobs like you're helping me.Quzah and I phoned him and told him what to post in a conference call
It's all about practice and experience... Keep writing code... One day the little light goes on and you can officially declare "I get it!"...Very efficient. :P haha thanks a lot for the help guys. Hopefully after a little more experience I can help future noobs like you're helping me.
Yeah my prof keeps telling me it's about practice. Doing a few programs everyday but it gets really tedious after a while I don't know how you guys do it.
If you don't enjoy it, it's not worth doing. Words to live by.
Quzah.
Hope is the first step on the road to disappointment.
Can't speak for the others... but I Don't.
I tend to walk around in a haze thinking about this or that function or module and then when I'm ready I'll sit down and zip it out in short order. Typing code is a very small part of programming... The big skill is not learning a language with less than 2 dozen words in it... it is in understanding a problem (i.e. project) well enough to write an adequate solution. For small stuff like you're doing now, an experience programmer might only need a couple of minutes to plan it out... but when the projects get big, the understanding and planning stages can take weeks or even months sometimes... Writing code is the second to last step in creating a program. The last step is fixing all your smegups and getting it to work...
quzah is right about that. However, if you generally like programming, it might just be because of the type of programs you are working on. Going through a book is in no doubt a good way to learn, however it gets boring. Take what you know already, and then work on making something fun. If you know loops and some basic logic functions, why not make a game? It really doesn't take too much to start working on making an asteroids style arcade shooter. You will learn a lot by doing that as well.
@Tater: I agree, however it would also be nice if we could fill it out in our profile and it showed up in all the free space next to our name.
<--------
Warning: Some or all of my posted code may be non-standard and as such should not be used and in no case looked at.
D**n, now my secret is out! ...LOLQuzah and I phoned him and told him what to post in a conference call
EDIT: BTW Tater, I like your new tag line.
Warning: Some or all of my posted code may be non-standard and as such should not be used and in no case looked at.
That was a secret? OOPS... my bad.
Actually it would pretty cool if everyone listed their compiler/IDE and OS in the .sig... would save a lot of confusion on OS specific stuff.EDIT: BTW Tater, I like your new tag line.
The windows aptitude test is one of those nifty "cookies" that people should explore.
