3 ms·
I would fall into your latter camp, being self-taugh. I started with the interpreted languages JS, Ruby and Python and, in the end, I didn't feel like I underst
by sAuronas 12y ago
I would fall into your latter camp, being self-taugh. I started with the interpreted languages JS, Ruby and Python and, in the end, I didn't feel like I understood what I was doing until I got into C and even Objective-C. Therefore, it wasn't until I touched a pointer or dealt with memory management that I felt like I was really more than a coder.
Not everyone wants to learn C, or C++ for that matter, but at least taking the time to understand I/O and (in my case) POSIX systems goes a long way to writing better programs - even if they are just in Python.
- jorgeleo 12y agoI began as self-taugh like you, but I went from Basic to Assembler in 1 year. I gained a lot by understanding what the compiler was trying to make work, so I agree with you that understanding of lower levels goes a long way into what you produce at a higher level Then I went to college, and math forced in me a more abstract thinking. I had to make it work in my head, because writing the symbols will not make sense if I could not conceptualize it first. I honestly hated differential equations, but in retrospective, it help me a lot to write functions that create new functions in return, and this is in C# (I don't like the mess that C++ became, but I respect other people that do)
- sAuronas 12y agoHaven't gotten into diffy-q but that's next up after I grock Swift and finish my Angular app.