If I worked -only- in ruby, then I'd likely remember those specifics much more, but since I hop around with rust, python, c#, clojure ... depending on our clients, there's no way I'm going to remember stuff like that for every language. Especially since languages tend to get updates and changes!
They change that often?
I memorized the programming syntax so that hopefully next time I opened up a language I haven't seen in years, I don't have to stumble around trying to catch my footing.
I also found that I have terminologies issue which may make communication difficult, so it's a good idea to have labels for structures in your program.
Typically not very much, but it -can- happen. I don't see the need to have stuff like that memorized when I can just check my wiki, or search online if that fails. Or I can even just look at one of my past codebases really quick with fuzzy searching or grep.
For any domain that I'm working in, it's typically unnecessary anyways. I do a lot of work in Rust right now so I have most things like that off the top of my head, etc.
For any domain that I'm working in, it's typically unnecessary anyways. I do a lot of work in Rust right now so I have most things like that off the top of my head, etc.
I also use the "wiki"(mine is just a series of atomized plain text notes) to learn stuff and look up. When that failed, I used google.
I just think that memorizing syntax is potentially valuable in switching context.
They change that often?
I memorized the programming syntax so that hopefully next time I opened up a language I haven't seen in years, I don't have to stumble around trying to catch my footing.
I also found that I have terminologies issue which may make communication difficult, so it's a good idea to have labels for structures in your program.