|
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.
|
|
|
|
|
|
Quite agree.
Isn't that what multi-monitor setups are for?
|
|
|
|
|
So, if my main project is challenging I don't need anything else.
O the other hand, if I'm working on some stalled project I feel the need to challenge my self with something else.
Usually I use this to lean new things or write articles.
If I keep too much time without putting my brain on stress I get bored... too bored...
|
|
|
|
|
I wonder why someone gave me 1 on this.
Not that I care about the points, I'm just curious about his/her opinion about it
|
|
|
|
|
...work on 4 consecutive private projects than one single project assigned to me by my employer...
AND spend some time on CP and The Chive....
Why can't I be applicable like John? - Me, April 2011 ----- Beidh ceol, caint agus craic againn - Seán Bán Breathnach ----- Da mihi sis crustum Etruscum cum omnibus in eo! ----- Just because a thing is new don’t mean that it’s better - Will Rogers, September 4, 1932
|
|
|
|
|
I used to view The Chive almost every day. I prefer being too busy to care.
Hogan
|
|
|
|
|
I don't like to jump every few minutes between things (as I have sometimes to do), because it makes it quite difficult to concentrate on something.
But speaking about big projects... it can be bit boring and dangerous as well. I mean dangerous because sometimes big projects have very specific things. If you have only a reduced bunch of things to work with/on and the time you need to do it is very long, there is a risk you start forgetting other things that not being used.
I think the best is to have one thing to focus on, but changing that thing every few weeks.
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.
|
|
|
|
|
If project have your dependency then have to work on multiple projects. Sometimes we do not have choice...
Thanks
-Amit Gajjar (MinterProject)
|
|
|
|
|
I've been working on a rather big project for over a year now... I wouldn't mind a change of view.
I can work on multiple projects at the same time. Although I don't want to hear stuff like "that project should've been finished last week!" because it's not going to happen when I have to focus on more than one...
It's an OO world.
public class Naerling : Lazy<Person>{
public void DoWork(){ throw new NotImplementedException(); }
}
|
|
|
|
|
... but like to have a small side-project to switch temporarily once in a while
Imagination is the one weapon in the war against reality!!!
http://aniruddhaloya.blogspot.com
|
|
|
|
|
my 'personal cpu' is bored of 'single thread' thinking or working!
|
|
|
|
|
I like to concentrate entirely on one project at a time. That allows me to have laser-like focus on the issue and how to solve it in code. It also helps me minimize mistakes, since the code I've recently written is fresh in my mind. However, I also need a brain reset once in a while. Something different to shake things up and get me thinking in new directions again. That is why I do side projects or small non-urgent programs as well. I don't put a lot of effort into them, but that change in topic often helps me better accomplish my main project.
Of course, all of this is dependent on what is actually possible. Sometimes I'm given multiple projects that have to be worked on at the same time.
|
|
|
|