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!"...Originally Posted by Sonny
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.
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.
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...
Well said.
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.
Also ... Any project worth doing is worth doing right.
Y'know what... that is a really good idea.
You should pop over to the General forum and see if Webmaster can do that for us...
Yeah definitely, I have this 1000 page text book and going through it is not fun at all. You're right I should try to make a game.
Please don't take offense at this, because that's not how it's meant...
Before you start doing stuff that diverges from the textbook... make real sure you don't abandon the learning curve in favor of personal projects. You will pay a penalty for that down the road when you discover you really do need to know the rest of what's in that book.
I'd suggest at least a good review of concepts that are obviously giving you difficulty here, before you branch out into anything new.
I agree. My intent was that while going through the book, you could solidify the knowledge gained there by making a game utilizing that knowledge, vice doing 100s of the boring textbook problems. Let's say I just finished learning about functions and loops. I could use that to make a game where I could actually explore these concepts but in a fun manner. I believe Matticus is doing just this.
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.
No of course i'm going to follow my syllabus as well. I meant that I learn better by doing rather than seeing it in a textbook. So what I can do is probably look up exercises in the text book and try those out.
Exactly.
Actually... doing the exercises and quizzes in the textbook is an expected part of the process...
Type them up, compile them, play with them, break them, fix them.... make sure you understand what they're doing and how before you move on to the next section... Reading retention runs about 50%... you can probably up that to 80 or 90% by working the exercises.
