Oct-12-2016, 02:21 AM
I think some people just want to accomplish a task any way possible, and some people want to learn. I have been on both sides of this.
I think you cant even tell good code from bad code from a single book either. Some books are best not written at all.
The only way to know good code is to write that bad code and figure out why its bad. You can tell someone all day long about using eval...and they wont know until they write something with it in it...and find a security loophole due to it for example.
Sticking close to this forum (or any active community rather) is a good way. That is how i learned. Reading through threads of how-to, why to do, and why not to do in pure examples taught me a lot. I made a decision to try to answer people questions that i did not know...and in turn by doing that...learned a lot by research and experimenting.
I think you cant even tell good code from bad code from a single book either. Some books are best not written at all.
The only way to know good code is to write that bad code and figure out why its bad. You can tell someone all day long about using eval...and they wont know until they write something with it in it...and find a security loophole due to it for example.
Sticking close to this forum (or any active community rather) is a good way. That is how i learned. Reading through threads of how-to, why to do, and why not to do in pure examples taught me a lot. I made a decision to try to answer people questions that i did not know...and in turn by doing that...learned a lot by research and experimenting.
Recommended Tutorials: