You... bought a laptop just for an editor? :-)

Yep. I bought a $3500 laptop, so I could run a $70 piece of software (educational discount, the price has since gone up). I was doing Solaris sysadmin work, and I had Solaris and Windows (just for Visio/Excel/MSWord) on my desk. I'm more productive in BBEdit, which is Mac-only. Oddly enough, I never saw a single Sun Professional Services person running a sparc-based laptop, and they seemed about 50:50 Mac:Windows.

As much as I agree, I still think that this (my current job) is an excelent opportunity for me to excel in this particular tool (Perl).

I'm guessing that even though you're saying it's just for Perl, that there are other, less tangible things, that even if you can't easily put them into words. But that's not bad. Go with your gut instinct -- it's normally right. (okay, I admit, I spend way too much time reflecting on the past, doing the 'what-if' thing, but it's unhealthy to spend too much time dwelling on mistakes, once you've identified what the problem was, and how to identify it and avoid it in the future).

Likewise, even though I said 'personel problems', it was actually much more complicated than that, and there were many other contributing factors.

I would still advise against using one, and only one tool -- it's more important to do it because you're comfortable and happy using it, rather than just because it's Perl. Learn some other languages, too, as you'll find that there are some things that are easier to do in other languages, and it can help you think about your problems differently. Change is not necessarily bad, and if you fight it just for the sake of change, you'll have problems. There are valid times to fight change, but you have to access each instance individually.

Besides, if you know other languages, it helps you when you have to migrate other programs to Perl

In reply to Re^3: Money vs. Perl by jhourcle
in thread Money vs. Perl by cog

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.