Beefy Boxes and Bandwidth Generously Provided by pair Networks
Just another Perl shrine
 
PerlMonks  

Comment on

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

I think with a new technology, the distinction between the technicians and the users is originally blurred. I am reminded of the early days of television, when you almost had to be an engineer to work the thing. You'd have to adjust it, tweak a whole set of knobs and switches, just to get it to work. Tubes would burn out, and you'd have to open the back, take out all the tubes, and test them to see which one was defunct. And so on. These days, you turn it on and it "just works".

Similarly, early computers required many users to program them. Available software was limited. Killer apps like Word hadn't been developed. Computers came with BASIC installed, and it was expected that you'd use it. If you needed something done, you often had to do it yourself. As the technology matured, many tasks became easier. We're not there yet, but we're getting to a point where you turn it on and it "just works". But until that time, there is likely to be considerable overlap between barely technical users and those properly trained (formally or otherwise) in computer science.

Your complaint about documentation really hit a nerve. It used to be that when you bought a computer, you'd get documentation that weighed more than the computer did (well, nearly so). It was filled with wonderful technical details, anything you could want and much more. Now, you get a "Quick Start" poster and a disk that has a PDF file on it. Most of that is either overly simplified crap (push the button on the mouse), or fluff from marketing. There's not much useful information any more. But the companies are targeting a larger audience now, the large number of basically non-technical users who do need to be walked through the basics.


In reply to Re: Social Computering vs. Computer Science by spiritway
in thread Social Computering vs. Computer Science by dimar

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



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • Outside of code tags, you may need to use entities for some characters:
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.
  • Log In?
    Username:
    Password:

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

    How do I use this? | Other CB clients
    Other Users?
    Others rifling through the Monastery: (4)
    As of 2014-09-16 05:22 GMT
    Sections?
    Information?
    Find Nodes?
    Leftovers?
      Voting Booth?

      My favorite cookbook is:










      Results (156 votes), past polls