People look at you like you're doing voodoo when you can do data entry on the keypad without using the mouse to navigate cells or look at the screen.

That's why I decided a long time ago that for any project I'm involved in that has a team of more than 5 programmers, if I have any influence, I'm going to strive to employ an administrative secretary. Key skills: touch typing, WP, shreadsheets, filing and no ability to take no for an answer.

There job is to off load as much of the non-programming work from the programmers as possible. Including typing up docs, maintaining timesheets, chasing deliverables, maintaining the project plan. etc. They cost about 1/3rd a decent programmer, but are about 5 times as productive in their areas of resposibility.

I once saw a programmer spend 3 days working up a program to collect and print his timesheets. And what happened to his painstakingly formatted printouts? They went up one floor where they were entered into a MIS system in about 30 seconds flat and then binned.

And have you ever watched a programmer use a WP program? They'll never finish that 3 page progress report until it has a title page, a TOC, and fully inverted index, a figures list and 2 other appendices. And until they've explored every obscure feature available. A good secretary will take a handwritten or flat text file and have it typed, spell checked, grammer corrected, formatted and printed before your average programmer has decided what naming convention to use for the file and where in his directory structure it should live.

Admin. secs., tech. writers and DBAs. Worth their weight to the project bottom line.

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.
"Too many [] have been sedated by an oppressive environment of political correctness and risk aversion."

In reply to Re^4: The dangers of perfection, and why you should stick with good enough by BrowserUk
in thread The dangers of perfection, and why you should stick with good enough by redhotpenguin

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!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • 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, details, 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, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            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.