...being in a single position for years can be more stifling...

Good point. The only negatives I've ever had with my job is 1) being the "only one" and 2) the pay. I've never worked with other programmers and as a result don't get the benefit of bouncing ideas off others and gleaning from their knowledge. I was recently told by a "fellow" programmer during a social situation that I "program, but am not a 'programmer'". Whatever that means. I took the high road and dropped the conversation before it seriously went south. I'll just assume it's a misunderstanding of my job since I don't work in a dev shop... Nevertheless, I've started feeling lately that I'm getting stale. Who has time to keep up with the latest trends when the to-dos are piling up faster than the have-dones?

Re: #2...My dad always said "I'd rather be underpaid for my job. If my boss realizes he's getting a good deal, I'll be the last one on the chopping block." With the exception of a few individuals (fortunately, everyone I report to or they report to, all the way up to the top), the organization as a whole doesn't have a clue what I do. It just chafes me that if I quit, it will be an eye-opener to replace me. This would certainly be a much easier decision if I held a non-educated, non-skilled low-paying job. I make too much to quit, but I don't make what I'm worth, either.

Ageism is for retail and food services.

I like to think, however naively, that good, working-stock, intelligent people can always find jobs. Realistically? Who knows. It may not be ideal and require a paycut, move accross the country, demotion, etc. I know I'll always be "hireable", the question always on my mind is if it will be in IT. ...And do I care anymore? I can't answer that question right now. I'm too busy bribing a 3 year old to pee in a toilet when she'd rather squat in the yard.

In reply to Re^4: How realistic is an extended absence? by ksublondie
in thread How realistic is an extended absence? by ksublondie

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.