Studying code is a great way to learn - a very large part of my initial knowledge about programming is the result of reading through huge amounts of code with the goal to learn what the code does, figuring out why the original writer did select a specific solution and to try to see if I could do better somewhere in the code.

But deciding that the code isn't working and then jumping from code to code is a really lousy way to learn.

You learn by studying the code until you get it to work - and understands why it work - or until you know why it does not work. If you know why it doesn't work, then you can decide if it is worth the time to make it work, or if the code was so lousy that it is better to search for something else.

- Bing Logarth hasn't mentioned any samples he has looked at.
- He hasn't shown any feedback that he has looked at any code at all.
- He hasn't mentioned what was wrong with the code he possibly did look at.
- He has only requested "give me code".

In the end, "give me code" is a lousy way to learn, since it doesn't not give any understanding. It doesn't answer any "why" or "how".