Subj : Re: Software Job Market Myths
To   : comp.programming,comp.software-eng
From : shelley
Date : Wed Jul 06 2005 01:59 am


CBFalconer wrote:
> shelley@osel.netkonect.co.uk wrote:
> >
> > "One person  - one project mode"  is probably one of the most
> > effective techniques for making programmers more effective. My
> > guess is that task switching probably wastes more resource than
> > anything else, developers and managers, yet seems to be the
> > default for many software people.
>
> This was probably in response to something or other, but noone will
> ever know what, due to the abysmal lack of quotations.  See my sig,
> below.
>
> I disagree with your fundamental thought.  I have always wanted to
> have several projects going at once, so that instead of beating my
> head against the cement wall in frustration I can switch to
> something else, and let the subconcious do its thing.  All may well
> become clear an hour, day, or week from now.
>
> It helps if the projects are quite different.  One may be software,
> another hardware, another documentation.  This is especially useful
> when operating in isolation.  Another useful mode is "tell it to
> the bear".
>
> --
> "If you want to post a followup via groups.google.com, don't use
>  the broken "Reply" link at the bottom of the article.  Click on
>  "show options" at the top of the article, then click on the
>  "Reply" at the bottom of the article headers." - Keith Thompson

It would be fine if it was a matter of choice - work until blocked on
on thread then switch but in practice schedules and tasks and switching
are imposed - and almost inevitably multiple projects result in
overloading, and mis-scheduling - underestimating one project is a
workable problem - underestimating three is a disaster. (Yes I know,
but it happens.)

As for the subconcious - it doesnt get a look in when I'm always
running to catch up - it works best (for me) when in one project mode.

What's 'tell it to the bear'?

(Thanks for 'reply' tip - didn't know I was doing it wrong.)

.