This is a discussion on Nested while loop inside for loop within the C Programming forums, part of the General Programming Boards category; Originally Posted by Sonny Very efficient. :P haha thanks a lot for the help guys. Hopefully after a little more ...
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.
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...
@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.
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.
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.