A start-to-finish approach has many advantages, higher focus and less distraction. In reality, most projects will stop at some point where I need feedback or material from other people, so there is time to switch to another topic. Another reason for a break is some task or project with a higher priority or closer deadline.
While I like continuous work and focus, it can get boring. Like @zedvas
wrote, procrastination on another project is a productive way to procrastinate.
I also have several side projects, mostly for learning and experiments, so they are not supposed to be "made" or completed anyway. Then there are long-term projects like a blog or portfolio, that require regular updates from time to time.
Without counting unstarted projects (they might already have a concept and some lines of code but await customer approval) and stale ones (unfinished code that has become outdated or irrelevant) I usually work on more than 2, but less than 10 concurrent projects.
A start-to-finish approach has many advantages, higher focus and less distraction. In reality, most projects will stop at some point where I need feedback or material from other people, so there is time to switch to another topic. Another reason for a break is some task or project with a higher priority or closer deadline.
While I like continuous work and focus, it can get boring. Like @zedvas wrote, procrastination on another project is a productive way to procrastinate.
I also have several side projects, mostly for learning and experiments, so they are not supposed to be "made" or completed anyway. Then there are long-term projects like a blog or portfolio, that require regular updates from time to time.
Without counting unstarted projects (they might already have a concept and some lines of code but await customer approval) and stale ones (unfinished code that has become outdated or irrelevant) I usually work on more than 2, but less than 10 concurrent projects.
Thanks for the insight 🙏💖