3 ms·
My $.02, when I started programming I tried the same thing by buying a book where a guy explained game programming by taking you through steps to write an entir
by logn 12y ago
My $.02, when I started programming I tried the same thing by buying a book where a guy explained game programming by taking you through steps to write an entire game he made. It made me want to quit programming. I found looking at small algorithms a lot more helpful. A good source for those is to read code of sorting algorithms and data structures. Then try to build them yourself (e.g., read the source code for a linked list, then build a circular linked list).
I don't see the need to worry about style if you're a beginner.
- greggyb 12y agoThanks for your input. Do you have any recommendations for a starting point for any of these algorithms. My first shot would probably just be trawling Wikipedia, but if there's a better place to look I'm all ears.
- logn 12y agoI didn't have any resources in mind when I wrote that, but after a brief search, I think this wiki looks good: http://rosettacode.org/wiki/Sorting_algorithms http://rosettacode.org/wiki/Sorting_algorithms http://rosettacode.org/wiki/Category:Data_Structures http://rosettacode.org/wiki/Category:Data_Structures Once you're at an intermediate level in any language and experienced with programming concepts in general, then it does make sense to develop good coding style (by reading books and blogs about the topic) and adopt idiomatic practices of the community (if they're sane). But simply reading a large codebase to become a better programmer is drinking from a firehose. It might make sense for an experienced programmer, but usually you'll do that because you're working on the codebase.
- greggyb 12y agoThanks very much for your feedback. This is helpful for me.