You did not specify precisely your role/responsibility profile for this startup, but if we continue along the lines of stereotypes, you will be wearing many hats as the various circumstances of the startup variously dictate from day to day.

Based on that stereotype, and the background of past experience, perhaps the most difficult transition a person with your profile could make is to *not* consider oneself a "programmer".

This might be an important consideration, because one of the most challenging aspects of transitioning into a 'startup' mentality is the shedding of any illusion of a coherent 'job description'.

The troublesome fact is there will be *many* times when you wish you could be writing some code, but some emergency situation will pull you away to something you do not want to do. The discipline required to cope with this may be the biggest challenge.

This is a gross oversimplification that varies depending on industry, economic factors, competitive environment and available resources (exogenous) ... as well as incentives, action plan, team cohesion (endogenous) circumstances.

=oQDlNWYsBHI5JXZ2VGIulGIlJXYgQkUPxEIlhGdgY2bgMXZ5VGIlhGV

In reply to Re: Time management, multitasking, and programming, oh my! by dimar
in thread Time management, multitasking, and programming, oh my! by Whitehawke

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.