Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple APILearn More
I find looking at someone else's code on one half of the screen and then re-writing it on the other helps. I don't mean copying it verbatim, but writing it in your own style so that you understand it.
@Awlex I'll keep your advice about 'deviants' in mind, while posting my future rants...
I do know about Deviant.. In fact, my sister is a frequent user...
I also tend to do the same... Stare at the code, trying to make sense.. Most times, it does the trick but sometimes, the manner in which a solution is derived or the main logic behind it confuses me... And, I am unable to connect the implementation with anything I know..
You could use the documentation for that programming language to find out how the code works. Or just try it out and see what it does. As long as you experiment with it to see how it behaves, you should be good. Just don't push stuff to master that you don't understand.
Google "Google university github". GitHub link has very good learning resource!
@jkrzefski So, what you are trying to convey here is to continuously try to solve problems on my own...
And, if I am stuck, then I might some time with it, but if I still find myself clueless regarding the situation or fundamental principles of the problem, then I should mark it in 'red'...
Discuss my problem with my peers or teachers, or ask people in the forum.. But, in the meantime, I should move on to the next problem...
And, in the free time, should check for alternatives for the 'red marked' question..
Just like we practice Maths...
Is this what you are suggesting or am I perceiving it wrong...
@SuyashD95 Not quite. My comment was meant more like an addition to your current way. So when you get an answer that you don't understand, you should still ask the author about the principles behind it, but you should not strictly keep away from that piece of code. Instead of not using it until you get an answer, it might help to experiment with it and see how it reacts when you change small bits of it. In general, looking at other peoples code is rather good, because it might give you a new perspective on things. Of course you shouldn't use code you don't understand, but instead of waiting for a reply for days, you might as well try to understand it yourself.