11-10-2016, 04:44 PM
I only have a versing in Python but what helped me a lot in getting basics of coding down was
a) doing a lot of side projects coding, very small things, hard enough to keep yourself interest and engaged but not hard enough that the frustration barrier was neverending
b) understanding proper mathematical thinking. There's a wonderful mini book written as a companion for transition from high school to university math, called Introduction To Mathematical Thinking. With a little searching a pdf can be easily found. I found there was a lot of transfer between thinking things out with super formal logic and understanding coding, and greatly accelerated the coding process.
I really recommend doing your first few projects in Scratch, so that you may learn the fundamentals of programming without having to tax your working memory with understanding the language. In order to get a really light grip with the language try implementing the exact same program within your language of choice, analyzing the differences between the intuitive feel of Scratch vs your language of choice. This allows you to more easily understand the logic of the programming language much more easily than brute forcing it.
I did cs50x through EdX and I highly recommend it for anyone who is interested in learning the basics of computing science or wants to dabble in it before dedicating serious time pursuing either a formal or informal education in the subject. I can't stress enough that this is EXTREMELY difficult to do and the thinking you are doing is very VERY precise. Do not be surprised that this is incredibly hard to do, and do not ignore the frustration if it persists well into your working time. Taking a break and letting your mind enter a diffuse mode of thinking is often a good idea.
If you are very time strapped and this is something you need to get out of the way brute forcing it with other people's code in chunks and tidbits is perfectly fine if you do not want to pursue the art of computing science or coding further. Will still be frustrating and will likely not be rewarding, but it will be easier.
As always this is a beginner of the craft speaking so take any of the above with a grain of salt. Personally, what helped me a lot when receiving semantic error (code runs and works, but undesired result) was writing out EXTREMELY precisely what was happening within my code. Most often weird ambiguous logic was the problem with my semantic errors in my code.
a) doing a lot of side projects coding, very small things, hard enough to keep yourself interest and engaged but not hard enough that the frustration barrier was neverending
b) understanding proper mathematical thinking. There's a wonderful mini book written as a companion for transition from high school to university math, called Introduction To Mathematical Thinking. With a little searching a pdf can be easily found. I found there was a lot of transfer between thinking things out with super formal logic and understanding coding, and greatly accelerated the coding process.
I really recommend doing your first few projects in Scratch, so that you may learn the fundamentals of programming without having to tax your working memory with understanding the language. In order to get a really light grip with the language try implementing the exact same program within your language of choice, analyzing the differences between the intuitive feel of Scratch vs your language of choice. This allows you to more easily understand the logic of the programming language much more easily than brute forcing it.
I did cs50x through EdX and I highly recommend it for anyone who is interested in learning the basics of computing science or wants to dabble in it before dedicating serious time pursuing either a formal or informal education in the subject. I can't stress enough that this is EXTREMELY difficult to do and the thinking you are doing is very VERY precise. Do not be surprised that this is incredibly hard to do, and do not ignore the frustration if it persists well into your working time. Taking a break and letting your mind enter a diffuse mode of thinking is often a good idea.
If you are very time strapped and this is something you need to get out of the way brute forcing it with other people's code in chunks and tidbits is perfectly fine if you do not want to pursue the art of computing science or coding further. Will still be frustrating and will likely not be rewarding, but it will be easier.
As always this is a beginner of the craft speaking so take any of the above with a grain of salt. Personally, what helped me a lot when receiving semantic error (code runs and works, but undesired result) was writing out EXTREMELY precisely what was happening within my code. Most often weird ambiguous logic was the problem with my semantic errors in my code.
My SB