How Do You Learn?

Ok, I want to ask a bit of an out-of-the-norm question just to see how colleagues approach this in their own environment/environments. It's a bit of an abstract question, the point being, I struggle with understanding the abstract. :D

So to give you an idea of what I'm trying to ask --

In my IT career so far, most of what I've done has focused on simply setting up and maintaining networks and computers/servers, with some application troubleshooting thrown in there. Lots of experience working with Windows stuff, Exchange stuff, networking stuff, etc.

So at my new job, there's lots of database stuff going on, which is NOT my forte. I aced my database classes back in college with flying colors, but then never landed into a job that actually implemented what I learned, so I've lost at least 95% of the knowledge I gained from those studies. So anytime someone throws a question at me related to anything database related (for instance here it's questions regarding Navision more times than not), I tend to produce a rather blank stare in response.

So what I'm starting to do is queue in on new terms I'm unfamiliar with when listening to people talk, or terms I haven't used in years and have since forgotten. For example, today I heard "SAP", "API", and "ODBC" thrown around in conversation between two other people here, and here we are back to my blank stare followed by intense wikipediaing.

So here's a problem that crops up, and it simply boils down to how my mind works and the inherent weaknesses consequently produced. My mind likes to process info in a very structured manner, and I learn best that way. Start with point A, get it down solid, move to point B, eventually you reach Z and have a full scope understanding of what you needed to know. So after a conversation like the one referred to above, my brain does this --

Q: Ok, so what's ODBC?
A: "The ODBC specification offers a procedural API for using SQL queries to access da--"
Q: Woah woah woah wait! What's API?
A: "The software that provides the functionality described by an API is said to be an implementation of the API. The API itself is abstract, in that it specifies an interface and the behavior of the identifiers specified in that inter--"
Q: Wait, stop! So what do you mean by abstract?
A: "In computer science, abstraction is a mechanism and practice to reduce and factor out details so that one can focus on a few concepts at a time."
Q: Ok, great...So what were you saying about API? And how does this all tie back into ODBC? Oh crap, and we haven't touched on SAP yet... :eek: :eek: :eek:

As you can see, learning the above is no such process of going from A to B to C, but bouncing around learning a bunch of concepts then connecting them, which then messes with my brain. I want structure. Start me on Point #1 then point me to the next place to go so I can learn efficiently.

And I think that's what intimidates a lot of people...a desire for a set linear structure in learning combined with sheer impatience. But nonetheless I want to broaden my mind to understand the arenas of IT that I have yet to venture into, such as this.

So, hopefully I'm asking a question in a round-a-bout way that will help a lot of other newcomers here.

Anyway, the bottom line is, how do you approach learning concepts that are broad and multifaceted? How does your brain process information, what is your learning style, how do you overcome the feeling of being overwhelmed? And ultimately, how successful are you with your learning methods?

Well, I am usually the one doing the teaching at work...

However, when I do learn...

I tend to sit there quietly, and ask questions that I know answers to to get a clarifying and solidifying answer. I feel that helps my understanding grow.

Everyone is different really, I learn best by asking questions as I go. Second to that I learn best by looking at reference material in something like a book but I do not like reading the whole thing just the parts I need to know..

Trial and error works best for me. It's probably not the most efficient route, but if I can make a few mistakes and then understand WHY they were mistakes, it's likely that that knowledge will contribute to the learning process in related areas, making the trial and error easier the next time around. Does that make sense?

As far as HOW I learn/process information, I kind of take a 'branching' approach. I make sure that I have a solid grasp on a fundamental concept or process and make logical jumps both to more basic concepts and more advanced ones (usually at the same time) and see how they relate to each other. If the jump proves correct, I'll add it to my proven knowledge and jump again, usually laterally and try to relate that backwards to the proven knowledge. Wash, Rinse and Repeat until I can relate almost any point in a subset of information to any other point without fail. Like a big, nerdy spiderweb.

As far as how it works for me...good so far. But it also helps that I don't get frustrated by much of anything.

O

Excellent topic I think. I am starting to study alot in the IT field. How everyone got so far in studying IT, such as Nihil and the older guys - Im sure everyone would love to know how they studied.

I assume trial and error has always been there :)

What usually works for me, buy/lent a book, read, try, make mistakes, read more, try more, make more mistakes etc... I mainly learn by doing it.

Never mind the fact I've been "doing it" for over 20 years now ;)

Quote:

---

Originally Posted by Cider

Excellent topic I think. I am starting to study alot in the IT field. How everyone got so far in studying IT, such as Nihil and the older guys - Im sure everyone would love to know how they studied.

I assume trial and error has always been there :)

---

I believe nihil was of the OLD school of PC education [PC = Pre Computer :p]
hell, I know I was :eek: as for now, I read books, home study, and when I can afford it, I attend a training course to cram in as much as I can in the time alloted

Quote:

---

Originally Posted by Ouroboros

Trial and error works best for me. It's probably not the most efficient route, but if I can make a few mistakes and then understand WHY they were mistakes, it's likely that that knowledge will contribute to the learning process in related areas, making the trial and error easier the next time around. Does that make sense?

As far as HOW I learn/process information, I kind of take a 'branching' approach. I make sure that I have a solid grasp on a fundamental concept or process and make logical jumps both to more basic concepts and more advanced ones (usually at the same time) and see how they relate to each other. If the jump proves correct, I'll add it to my proven knowledge and jump again, usually laterally and try to relate that backwards to the proven knowledge. Wash, Rinse and Repeat until I can relate almost any point in a subset of information to any other point without fail. Like a big, nerdy spiderweb.

As far as how it works for me...good so far. But it also helps that I don't get frustrated by much of anything.

O

---

Ditto...IMHO you can't effectively learn the finer points of something until you understand the overall architecture of it...get the theory/terminology down pat and the other stuff IMO will come easier...

In general, my background has been broad enough that I could skip the theory part; however, in the few cases I have stumbled across something entirely new, I have usually started with a book on the subject to get a broad view of everything and how it interconnects...once I am comfortable with how its supposed to work, then I start diving into the nitty gritty of it and trying to apply it to the problem that I am trying to solve...

While I have been successful in the past with learning something on the fly without the theory, it has almost always been necessary to go back and look at it later...so far its worked extremely well for me...

Quote:

---

I believe nihil was of the OLD school of PC education [PC = Pre Computer ]

---

Quite, I go back to Kalamazoo and the old electro mechanical accounting machines such as NCR and Nixdorf :cool:

As for learning, mine has been a mixture of formal training/courses, interactive learning courses, reading, and most importantly hands on experimentation.

HI

Well if i talk about myself then i should go back to school
i realy had difficulties in learning scientific formulas "theoritical" but when it use to come for laboritries work experimentation and all i use to be in toppers

where as if u take it in the sense of mathematics it use to be a peice of cake and my name always use to be in toppers

from that i actually generated my talent in accounting and finally right now i m a accountant

finally to the conclusion i have arised that i m good when it comes to the real problem site i wolud try to analyse and work on it hard and finally come to the solution of it

so whenever i need to learn something i try to make it my problem and then it really turns up easy for me to learn about it

The way I work is a kind of iterative process. If I understand something fine first time around, great. Otherwise (assuming it's something practical) I try building from small examples and (with a lot of swearing) get something to work.

Usually what happens is that a while later (days, weeks...just depending) I come across the same questions again except this time I understand it a lot easier. I think one of the best ways is trying to look at problems from a lot of different angles - usually if you can get multiple different explanations of something you end up with a good understanding.

For example, one of the guys at work that I tend to ask questions will answer by jumping off on loads of tangents, not all of which I understand. A lot of the time my mind wanders and I forget (consciously) what he's talking about. What I usually find is that a while later I'll be doing something and suddenly remember part of the conversation that I didn't understand at first and realise what he was talking about.

I find the best way for me to learn is by experimentation because I struggle to read and understand lots of theory without a practical use/example to back it up with.

ac

Quote:

---

I find the best way for me to learn is by experimentation because I struggle to read and understand lots of theory without a practical use/example to back it up with.

---

Ditto...It's very hard for me to just read something and get it. I'm usually a very visual and hands-on learner. Show me pictures, then give me an example to work on firsthand.

Hands on is the only way the Wolfman roles.....especially when it comes to the ladies *wink*

YEah hands on is the way for me! I cannot remember much when reading :)

Hands on. Trying. I hate take notes so i need to learn all without them.
Sometimes go to books, internet to find how to do some stuff when i can't figure out by myself