I prefer to work on one task at a time, but I can work different projects task by task. What I absolutely don't like is switching often and in the middle of unfinished tasks. It requires a lot of time to dive back into WIP.
Also: The better everything is documented / commented the easier it is to switch between projects. When I was young I was very chaotic (like many programmers), meanwhile I try to keep my stuff tidy, it helps a lot to come back to a project, read some code and comments and immediately understand what it was about or where to continue ("// TODO:" comments!)
Too much of the same thing is not good for health. Working on multiple projects at same time may help keep your brain rejuvenated and sometimes even reduce stress levels. But the only condition is that you must enjoy your job.
you said yourself "too little time for anything". In real time these days finding time for our loved ones itself is a big project. Gone are the times when we could comfortably work on one thing at a time. If you want "time for anything" you must learn to handle multiple things at the same time. Charles Darwin Theory Of Evolution is applicable to humans also.
You are correct! I will use the word "smarter"....
you said yourself "too little time for anything". In real time these days finding time for our loved ones itself is a big project. Gone are the times when we could comfortably work on one thing at a time. If you want "time for anything" you must be smarter and learn to handle multiple things at the same time.
Charles Darwin Theory Of Evolution is applicable to humans also.
Oh and I forgot ... there is an enjoying the job part. If you are not able to do multiple projects at the same time most probably you are not enjoying your job....?
10 yrs down the line I will be..... And yes I do love my job,....because I don't do something I don't like...and I do like doing a lot of it. But thank you for your thoughts....I can't discuss about ego because it'd be like moving out of topic.
If you just work for whoever, you'd end up wasting all your time/energy/youth churning out code and when you wake up at 35 years old, balding and gut hanging out, you'd all of a sudden it isn't very cool at all you spent your life code for some sh*t head (who probably tells you you're a hero all the while) and not being able to afford a mortgage, buy a car, feed your parents, or have enough money to get married.
Asia is different kid, play smart. Avoid shallow pockets who don't pay (At all cost)
Usually I have a large project on the go but I'm also called onto smaller more immediate jobs such as writing new utilities for our production team; on the one hand it's a pain to be pulled off the main project when I'm in a good flow, but at the same time it's sometimes nice to have a little break.
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.
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."
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.
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
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.
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.
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.