The Developer Urge to Start New Projects (and how to stick to your current ones)

I'm currently a student at SRMIST, pursuing ECE. I love coding, learning and making web development projects, reading and writing and creating YouTube videos.
Search for a command to run...

I'm currently a student at SRMIST, pursuing ECE. I love coding, learning and making web development projects, reading and writing and creating YouTube videos.
No comments yet. Be the first to comment.
Discover the power of Context & Reducer Hooks in React.js by creating a global snack bar using TypeScript and bootstrapping with Vite.

Streamline your web development process with a step-by-step guide from ideation to deployment. Optimize your project planning for better results.

Get started with your coding journey the right way and learn what works best for you from my experience and mistakes.

It's been close to 2 years since I started my journey in Web Development. Just like everyone I started off with learning the basics and slowly out of curiosity learnt some of the advanced stuff. Last year, I spent most of my time mastering the fundam...

Yesterday, I turned 20 years old. And it feels just like any other day out there. Although I wouldn't be here if it were for the people around me and how much they've helped me grow, especially in the past 2 years of my life. Recently I have changed ...

It's a casual day of coding on a project that I've been working on for about a month. While learning how to implement a new feature, I got an idea of how to use what I exactly learned in a new project. I go over to my GitHub account, and create a new repository, while the dozens of incomplete projects watch me do it. (Find it relatable?! ๐ ๐)

What is it about new projects that we drop the current ones we're working on? Why are they (generally speaking) more fun? and how do we stick to the current work before moving on to new projects?
I've been thinking about this and to solve them, I reached out to my mentors, seniors and peers in my college. What I learnt was much more than what I thought the answer to this could be!
Personally, I feel that whenever I learn something new I must try and implement it somewhere to explore all sides of it. This goes on like a domino effect, one new learning, triggers another project and there's always something new to learn in every project.
Obviously, my opinion didn't leave me satisfied and to know more about this and how to stick to the current projects I was working on, I got words from my seniors on this.
As Developers we need to understand that not all side projects need to be completed. Every projects is an opportunity and a valuable experience to learn something new regardless of it's success or failure. Only when you're strongly committed to a project will you be able to complete, or until you're getting paid for it XD. - Snehil
๐คฏ Yep, that's how I felt too. It's okay to have numerous uncompleted projects, they're all part of you're developer journey and helped you get where you are today. Some points to mention to stick to your current projects,
It's easier to start new projects because they're simple to initiate and not as simple as completing already ongoing projects. - Avichal and Arindam
Human nature is that we choose the path of least resistance we can take up, and yes, new projects are much easier to set up, there's no bound to complete them, and it's much simpler than finishing ongoing projects. Some ways to stick to your current projects,
A new project gives us a clean canvas to work, a start of the project is the time when you can go creative, a new design, new APIs and a completely new outlook. Current projects can get really boring, I think constant progress is the only thing which can keep you going once you stumble. - Hardik Garg
Constant progress is the process of doing something consistently. Without consistency a flow is broken and it's difficult to regain the momentum there once was.
It's a very common experience to go through. From my personal experience, I can say that we tend to loose interest in a project if we work on it for too long. - Gaurav Prasad
In order to deal with this,
Make sure that the time allocated is not to long to make it boring. Always try to understand the project as a whole before coding into it.
If you're working on a project with a vision and a goal, you'll avoid skipping on it. However, if you're working on a project just for the sake of doing it, you'll jump from one to another. - GS Thina
Yep, agree with this one. Until you know that it provides a long run benefit to you or to others, there will be no reason to stick to it in the short term.
It's better to not commit to new projects until you're done with the older ones. - Vivek
What are you own personal theories on this topic?
New Projects are fun, they help stimulate our creative minds and as developers it's a part of the process to have many unfinished projects and it's nothing to feel guilty about. It's human nature to get bored or to go to what seems more interesting than to stick to what you're currently doing right now. I've gotten a lot of great insights from this and will be back to answer such questions with great insights! Stay tuned.