Beefy Boxes and Bandwidth Generously Provided by pair Networks
There's more than one way to do things

comment on

( #3333=superdoc: print w/replies, xml ) Need Help??

I think that some of the issues that you're seeing aren't necessarily related to 'learning style', per se, but in that you don't have the necessary context to make sense of the information that's being presented.

For instance, to learn a complex concept, you typically need to have at least a peripheral understanding of the basic concepts from which it is derived. At the very least, you need to understand the language in which the instructions are being given. Does it do us any good to go to a lecture about 'associative arrays' or 'tuples', when we've only heard the term 'hash' used to describe the concept (okay, they're not exactly the same thing, but that's part of the problem with terminology).

The even bigger problem is when different communities have the same terms (words), but they have describe different context -- telling someone to 'go into the other room and strip' has absolutely nothing to do with removing clothing if you're in the printing industry. (the example comes from Axley's 1984 article, "Blow up the communications pipeline", which discusses problems with people thinking they understand the message, but actually didn't). Even Heinlein touched on the issue of language in learning in 1961, in Stranger in a Strange Land -- teleportation made perfect sense to Mike, but he had to teach people the Martian language because the terms just didn't translate into English -- once they knew Martian, the concept was easy.

Trying to place knowledge into documentation is a particularly difficult process, as you have to write for the person who is going to be reading the documentation -- if you have disparate groups of readers, it's sometimes more efficient to write two or more seperate sets of documentation, if it's for a system that's not going to be changing much. (if it is going to be changing, then you have to maintain all the docs, so it may be easier to maintain modular documentation, some of which are just to set the necessary context to understand the other parts):

I think your points are valid, and I'd also like to add

  1. It's difficult to learn a completely novel concept; you must build upon concepts you already know.
  2. You must write documentation and training materials with an understanding of the intended audience, and avoid (or define) jargon or concepts that they may not be expected to know.

In reply to Re: On differing learning styles, and learning programming through perl by jhourcle
in thread On differing learning styles, and learning programming through perl by g0n

Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":

  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or How to display code and escape characters are good places to start.
Log In?

What's my password?
Create A New User
Domain Nodelet?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others rifling through the Monastery: (5)
As of 2023-03-31 18:59 GMT
Find Nodes?
    Voting Booth?
    Which type of climate do you prefer to live in?

    Results (76 votes). Check out past polls.