Yep, I fit all sorts of hats! :) But maybe because the company is small (Engineering = 100 folks?) rather than large.

100 *Engineers*? If there were 100 *employees*, I would consider that a medium-sized outfit. Small is like where I work -- I am *the* computer guy. The only staff person who makes regular use of copy and paste technology, that's me. If it has to do with computers, it's my job. Stuck printer? Get Nathan. Need a database? Talk to Nathan. Web browser stuck? Ask Nathan. Want to set up a cgi server? Nathan. NAT/Firewall stuff? Nathan. Windows needs a reboot? MacOS 9 is hung? Fetch Nathan.

I used to spend almost all of my time troubleshooting. I've been gradually improving that situation.

We had slightly more than one printer per computer when I was hired; nobody on staff was even dimly aware of the possibility of a networked print share. I've got us down to one printer downstairs and five or so upstairs, instead of about twelve, and I got rid of *all* the StyleWriters, so the number of times per day that I have to fix a printer has gone from about 10 to less than one (average). I also used to have to unstick or restart web browsers a lot more often, but now that I've got everything upgraded to Mozilla 1.3 or higher (except one Classic Mac that's using 1.2.1), I don't get called out for that nearly as often. Once a day maybe, no big deal, and it's usually a PEBCAK error, Java problem, or Acrobat Reader issue. So these days I spend a lot more time sitting at my desk, writing Perl code to do various things that I wouldn't have had time for two years ago. I've got a Perl/MySQL/CGI inventory-tracking database now for all our computer equipment, instead of scraps of paper and MS Works documents like before. I wouldn't have had time to write that if I had to unstick printers eight times a day, but I've invested time in saving time, and it's paying off. When our program coordinator quit, who always used to do anything desktop-publishing-related in Pagemaker, the director discovered in a moment of desperation that I'm capable of doing that stuff too. (I'm in the progress of migrating over from Pagemaker, which sucks, to OpenOffice, which is *way* easier to use and has almost every feature; there are just a couple of things missing that I'd have to go to Pagemaker for, such as the ability to rotate a paragraph at an angle that's not a multiple of pi/2. Hopefully I won't need those features very often, because working with PM is a PITA. The version we have doesn't even have proper tables or the ability to underline tabs, so you end up building stuff up out of primitive lines -- ugh. Plus, MacOS 8 isn't my idea of a fun environment to work in.</rant>


;$;=sub{$/};@;=map{my($a,$b)=($_,$;);$;=sub{$a.$b->()}} split//,".rekcah lreP rehtona tsuJ";$\=$;[-1]->();print

In reply to Re: Avoiding "brain drain" in the corporate realm by jonadab
in thread Avoiding "brain drain" in the corporate realm by flyingmoose

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.