i finished the sites tutorial and tried a good number of examples as applications to whats in the tutorials....what should my next step be
i finished the sites tutorial and tried a good number of examples as applications to whats in the tutorials....what should my next step be
practise some more. Think up yuor own examples, like converting numbers between bases, write a calculator, think about getting towards writing a simple game..... oh and make up your own goddamned mind
i mean i have heard about win32 programming,network programming,game programming.....etc.after reading this tutorial am i qualified to get into these stuff
Get a book. Or two. Or better yet, ten.i mean i have heard about win32 programming,network programming,game programming.....etc.after reading this tutorial am i qualified to get into these stuff
dwk
Seek and ye shall find. quaere et invenies.
"Simplicity does not precede complexity, but follows it." -- Alan Perlis
"Testing can only prove the presence of bugs, not their absence." -- Edsger Dijkstra
"The only real mistake is the one from which we learn nothing." -- John Powell
Other boards: DaniWeb, TPS
Unofficial Wiki FAQ: cpwiki.sf.net
My website: http://dwks.theprogrammingsite.com/
Projects: codeform, xuni, atlantis, nort, etc.
ok i took c as a course in college and finished the sites tutorial...why do u think i should get a book...i noticed books are the same as tutorials but with a larger number of pages.
You've likely been given bad advice along the way. Books can help filter out good and bad advice (so can forums such as this): read the same thing in 10 books, it's probably solid advice; read differing recommendations every other book, it's probably not so trustworthy. Books have a better tendency of maintaining continuity than various threads. And they make better references.
If you want to round out your language knowledge, answer questions in a language forum. You'll be surprised at how much you don't know. If you want to branch out into an area of interest, seek such forums and tutorials and FAQs. If you want to get better in C, get K&R2 and answer all of the questions -- by the end you'll be quite well versed. [One of these days I really gotta try that myself.]
7. It is easier to write an incorrect program than understand a correct one.
40. There are two ways to write error-free programs; only the third one works.*