I'd like to say something that will make me zero friends.

Being a good programmer is being able to do the boring work. Every time. I have my own company (two man outfit) and I partly agree with the above posters that you will do more interesting stuff at smaller companies, but it doesn't change the math. 90% of everything is boring crap. But it needs to be done.

A good company will spread the interesting work around, a place I worked recently had a rule that the same person couldn't do new dev (whole cloth projects) twice in a row. And they made sure there were enough new dev projects in the pipeline everyone got one occasionally (that was a larger shop, about 50 employees w/ 10 engineers).

Great programmers have done something before, so they can do it well when asked to at this job and for this particular problem space. It isn't exciting, but they will also do it just because it is their job. period.

I get to do stuff I find interesting frequently but I'm OK with the fact it won't be most or even much of what I do. If you can find a job that involves more interesting things than what you are doing currently, go for it. But there will always be the boring stuff. Starting open source projects or doing other personal stuff is a good way to have fun, but it is called a hobby because no one is willing to pay you for it (conversely, this is why they call a job "work").

-jackdied

In reply to Re: Avoiding "brain drain" in the corporate realm by jackdied
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.