Survey Results

Multiple project to keep me occupied when I'm waiting input

13-Nov-12 16:37

(aka Result Oriented, or simply "A lot of result oriented")

Nothing new under the sun

dev

Nicolas Dorier13-Nov-12 12:16

Nicolas Dorier

13-Nov-12 12:16

I prefer multiple project.
The reason is that most of the time I code a little, and then need input from other people for whatever reason (database access, business question or whatever)

I don't want to waste my time (and thus my customer money), by taking action with incomplete input.
So when that's the case I switch on another project at hand.

That's also why my customer are happy : I'm don't cost them any money when I'm waiting :p
On my case I'm happy because I have no down time.

Nicolas,

However . . .

W∴ Balboos, GHB13-Nov-12 5:45

W∴ Balboos, GHB

13-Nov-12 5:45

Nobody really cares much about what I like.

"The difference between genius and stupidity is that genius has its limits." - Albert Einstein

"As far as we know, our computer has never had an undetected error." - Weisert

"If you are searching for perfection in others, then you seek disappointment. If you are seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010

Re: However . . .

wizardzz13-Nov-12 11:19

I like having a 2nd project

13-Nov-12 11:19

Well, they asked, didn't they?

Re: However . . .

Mohamed Mitwalli13-Nov-12 20:21

Mohamed Mitwalli

13-Nov-12 20:21

Agree with you Frown | :(

Clifford Nelson13-Nov-12 5:37

Clifford Nelson

13-Nov-12 5:37

If I run into a snag on a main project, it is always good to be able to be able to go to another project that is low priority. I have also sort of liked having multiple responsibilities because the other responsibilities give me a break/change.

wizardzz13-Nov-12 11:18

13-Nov-12 11:18

100% agree with you on this. Unfortunately, I just checked, I had 8 open VS projects today, all of which I worked on, today (well, one I just code reviewed).

Clifford Nelson13-Nov-12 11:56

Clifford Nelson

13-Nov-12 11:56

That gets painful. Hard enough remember what you did on 1 project, let alone 8

wizardzz13-Nov-12 11:57

13-Nov-12 11:57

I will be honest, it has been pretty close to hell today. To make matters worse, my boss went ahead and fixed a small problem, without grabbing latest code first, then checked it in. Merge hell! D'Oh! | :doh:

devvvy13-Nov-12 22:11

13-Nov-12 22:11

and deployed to prod?!

dev

wizardzz14-Nov-12 3:54

14-Nov-12 3:54

His is in QA but going to roll out to prod as it is an emergency release. I'm working on the merge now to get out to QA (my code was an additional feature and performance improvements)

modified 14-Nov-12 10:10am.

devvvy14-Nov-12 13:34

14-Nov-12 13:34

i just sneaked out a change yesterday as well.

dev

Multiple projects but a single at a time.

Clifford Nelson14-Nov-12 5:09

Clifford Nelson

14-Nov-12 5:09

Had a friend (he was promoted to more a management role) who had to watch as another programmer slaughtered his application because he was not a good programmer. Very frustrating.

R. Erasmus12-Nov-12 20:21

R. Erasmus

12-Nov-12 20:21

I like jumping to other project and doing some work on them for a month or two and then jumping back to main project. The thing is that when I jump back to other projects my attention is completely there, and for that time I'm off the project I was first working until my work there is done.

"Program testing can be used to show the presence of bugs, but never to show their absence."

<< please vote!! >>

It's the number of distractions

BRShroyer12-Nov-12 6:34

BRShroyer

12-Nov-12 6:34

I don't mind working on multiple projects, but I can't stand when one immediately becomes a priority over the others. This happens way too often every day. Even when I set aside blocks of time to be undisturbed, it doesn't happen.

It would just be nice to focus for a few hours on a single task.

Brad

If you think you can, you will.
If you think you can't, you won't.
Either way, you're right.

It really depends on the project type and resource share

Dan Neely12-Nov-12 5:50

Dan Neely

12-Nov-12 5:50

2 projects at 50/50 are fine. A 25% or smaller share isn't bad in the planning, wrap up, or post-deployment bugfix stages (assuming you did a good job coding anyway), or any time you're basically on-call to provide support as needed. However, it is maddening when trying to do main development since your choices are either breaking it into very small time slices and not being able to do a major feature in one session or having your time slices spread far enough apart that you lose a significant amount of time to trying to reload your mental context from the last time.

Did you ever see history portrayed as an old man with a wise brow and pulseless heart, waging all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
--Zachris Topelius

Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt

Multiple project.s working capability!

csharpbd12-Nov-12 5:14

csharpbd

12-Nov-12 5:14

Working on multiple projects at once it depend on human working capability. But I think Working on multiple projects at once it good practice.

devvvy13-Nov-12 16:49

13-Nov-12 16:49

you can work for an asian firms - they love guys who can work on number of projects same time for half the wage.

dev

csharpbd13-Nov-12 18:04

csharpbd

13-Nov-12 18:04

devvvy13-Nov-12 22:10

13-Nov-12 22:10

but then you probably already know don't you!

dev