4 ms·
Have you identified what it is that you are specifically slower at?
by DougMellon 5y ago
Have you identified what it is that you are specifically slower at?
- Arisaka1 5y agoI have a slight idea that I might be focusing too much on remembering the exact syntax and understanding (almost) every line before I move on, and that I should chill out a little bit and realize that I'll be working with Python docs, google and API docs open 24/7 for a while. But then I might end up not recalling many things later. Can I even claim that I'm "learning" like that? What if I end up being someone using older projects as a reference? Is that even acceptable?
- silisili 5y agoNo offense, but it sounds like a combination of overthinking everything and being nervous. When I started, I was similar. I read K&R C cover to cover, then sat to write a toy program and didn't even know how to start. Lesson learned. Now when learning a new language, I scan the docs, then sit down to write something. Line by line, word by word if I need help(and I do), I'll find a reference, write it, move to next. And you'll learn that way, from repetition. In short - less thinking, more doing.
- InitialLastName 5y ago> I read K&R C cover to cover, then sat to write a toy program and didn't even know how to start. This is interesting, because K&R's strongest point is its exercises. I'd almost call it not worth reading if you aren't going to do them, but if you did the exercises (which get deep quickly) and came out unable to write a program that's a bit baffling.
- silisili 5y agoI read the exercises, and thought through them, but did not do them. Busted!
- machiaweliczny 5y agoI know little python and I would never focus on syntax but on data and architecure first. Then on responsibilities of given service and only then I would learn specifics to given task by googling. That’s how you do it. I programmed in 10+ langs and I confuse syntax all the time (except in lang I work day to day)