|
Agree with you 
|
|
|
|
|
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.
|
|
|
|
|
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).
|
|
|
|
|
That gets painful. Hard enough remember what you did on 1 project, let alone 8
|
|
|
|
|
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! 
|
|
|
|
|
and deployed to prod?!
dev
|
|
|
|
|
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.
|
|
|
|
|
i just sneaked out a change yesterday as well.
dev
|
|
|
|
|
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.
|
|
|
|
|
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!! >>
|
|
|
|
|
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.
|
|
|
|
|
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
|
|
|
|
|
Working on multiple projects at once it depend on human working capability. But I think Working on multiple projects at once it good practice.
|
|
|
|
|
you can work for an asian firms - they love guys who can work on number of projects same time for half the wage.
dev
|
|
|
|
|
|
but then you probably already know don't you!
dev
|
|
|
|
|
I know this things, bcz I am a Bangladeshi.
|
|
|
|
|
I'm a man, I'm genetically programmed for single-tasking - according to my wife.
One of these days I'm going to think of a really clever signature.
|
|
|
|
|
Bull. You can surf through dozens of TV channels, read the newspaper, eat breakfast and browse the internet all at the same time, can't you?
(Disclaimer: no responsibility accepted on what happens after you tell the wife this)
BTW I have no preference in these lean times, and any work is better than no work.
|
|
|
|
|
Indivara wrote: any work is better than no work.
Regards.
--------
M.D.V. 
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpfull answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
I prefer to work on a single project at a time, but I have to work on multiple projects at once.
|
|
|
|
|
This is more the standard process.
Personally, I prefer to work on a single project at a time. For those that say they get bored & like to switch between projects, I find that a project has several different aspects that need work so I can switch between different tasks within the same project to stop myself from getting stuck.
Prefer 1, usually need to work on many.
|
|
|
|
|
Working on a single project at a time is not very productive, nor involving.
But "multiple projects" is too generic: I think that the ideal situation is having exactly 2 projects to work on, so that when you get bored of one or you get stuck on it, you can always switch to the other. Working on more than 2 projects is too dispersive, though.
|
|
|
|
|
Aiscrim wrote: when you get bored of one or you get stuck on it, you can always switch to the other.
I switch between tasks based on their delivery requirements, not because I'm bored or encounter an impediment.
/ravi
|
|
|
|
|
Well, of course I was supposing that both projects had the due date set to "yesterday", as it always happens in normal development schedules.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
