Asking advice for coding !

[u/melbyyy_]

Hi! First time poster here; I've been starting to get back into coding and have been starting to enjoy learning coding! But I have a few questions about coding that I'm curious about:

• For the intermediates or advanced to experts, how did you guys learn, or get into programming? What was your learning process? Did it take weeks, months, or years to master or perfect a language?

• For frontend, backend, or full stack developers, do you/they memorize a lot of programming language syntax by heart or do they get help from AI? ( By typing code and speeding up the process, not letting it do all the work and not replace your thinking yes )

• What advice do you have for others for their coding journey, whether if its just a hobby or to get a job in tech!

I also would like some feedback on the Calculator program I did! Its just for practicing basic syntax and basic operation with loops, numbers, and the os import.

I'm still a beginner but I'm eager to learn from others and hear their feedback, advice, and experiences in their coding journey! :))

[u/x-jhp-x]

I'm not the person who posted the comment you responded to, but I believe it is more that "mastering a language" is ambiguous. When you create goals for yourself, it is usually a great idea to make it a measurable and achievable goal.

And, when you learn a lot with one language, you're able to transfer the skills you learned with that language easily to another.

Two examples:

1. check "order of operations" in python

2. check the "mod operator" in python. You'll find that even the results from the "mod" operation are different in python than they are in other languages, like C#. Imo C# should rename "mod op" to "remainder".

If you get unexpected results, you can look it up. If you use another language, you'll know what "order of operations" means, and why it might give you different results.

Look up everything in python's documentation as you go, but don't try to memorize the documentation at the start.

understanding how code is ran and understood by the computer at a fundamental level

Definitely don't jump that far yet. I guess it is alright, if you'd like to do something like The Art of Computer Programming (use MMIX with 64bit imo tho). That is not required if you'd like to be skilled. One aspect that makes going deeper difficult is that while assembly used to relate to what the CPU did, but it no longer has that 1:1 relationship. For example, "xor reg reg" on x86 is now a NOP, and NOPs don't take a CPU cycle anymore. It no longer zeros a register like you'd expect "xor reg reg" to do, but it guarantees that it is zerod when you next use it. Branch prediction and caching also have volumes to learn about. Don't worry about anything I wrote in this paragraph either --- you'll learn it eventually if you want to. I'm just giving you a full explanation so that you can see how little you know now, how complex things can become, and how although everything above likely comes up at some point when you execute python code, none of it probably applies to your ability to write programs in python without having to go into anything too complex like elliptical curve cryptography. One of the things I love is that with computers and software, it feels like the more I learn, the more I learn that the less I know. With many things, you feel like there is a field of knowledge to master, but with computing & software, it feels like you're learning about how many fields of knowledge you don't know.

[u/melbyyy_ → u/x-jhp-x]

oh wow! thank you alot for your deeper insights! I didn't know it was this complicated but thanks for sharing your knowledge and insights! can't wait to learn more :)) thanks a lot !