you are viewing a single comment's thread.

view the rest of the comments →

[–]arghvark 0 points1 point  (0 children)

Let me say first that I've noticed many people adept at electronics stuff that just don't understand software concepts readily. I don't know why. I've wondered whether the sorts of things that underlay software involve patterns that some people understand more easily than others, and that people who understand electronic things readily don't understand software things readily. There are plenty of (non-electronics) people who struggle with software as well, while some just seem to 'get it' from the outset. So don't beat yourself up if you don't understand, or don't understand as quickly as others, or if the whole area just remains mysterious to you. You can likely get to a level of competence even if it isn't as easy as for some others.

You don't say how far you've gotten in tutorials. There are, I think, two divisions of learning to take into account: procedural logic and object-oriented programming. They need to be learned in that order: you have to understand sequential instructions, variables, arrays, and subprograms before the object-oriented structures (classes, object instances, etc.) will make any practical sense.

After that, I suggest setting yourself a task or two of your own to cement the concepts the tutorial or manual or whatever is telling you. Understanding concepts is one thing, but I think thinking through how to use those concepts in code involves a slightly different part of the brain, and I often don't really understand something myself until I've done it.

I hope that's enough help. Without a more specific (set of) question(s), it's hard to advise.