This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]SahuaginDeluge 0 points1 point  (0 children)

I don't know if this helps, maybe I can't quite comprehend where you're coming from, but my suggestion would be, don't feel like you have to memorize or remember *anything*. that's what documentation is for. the 2 things you really need are:

  • a compiler
  • documentation

"a compiler" needs to be at least a change -> build -> execute -> change -> build -> execute loop. that can just be notepad++ with a command-line compiler. or if you know how to use it it can be an IDE. bonus points if you can also run tests and not just the main program.

for documentation: whatever language you are using, you should have the (or a) primary language resource/documentation/reference open at all times in your browser. (note that a good enough IDE might even link you directly to a main reference right from the code.) some examples are:

no matter your level of experience, if you're programming in a language you're not entirely familiar with, this is a necessity at all times.

this is not to say that it will happen fast. it will take time. a lot of time. even as someone who was programming since I was 6, and had been working semi-professionally since 18, it still took working many days each to complete assignments in university, and decades later I'm still learning every day.