I often start a new small project instead of focusing on my main one.
For me, it's a way to avoid the complexity and effort required for the main project. And there's the fear of failure: I would be down if my main project failed, but with a small side project, there's no attachment.
Smaller projects can also provide an immediate sense of accomplishment.
I'm just starting a new small project right now. This time I'll be using some strategies:
Build in public: I'll be live tweeting and posting to IH about it to check progress and keep me accountable.
Time limit: If it's not ready to show to someone before the weekend, I'll stop
ChatGPT: I'll use it as a "partner" to keep me on track and exchange ideas. It's an excellent way to avoid analysis paralysis.
Have you tried some of these strategies? Any other suggestions?
✅ Time limit
What would you say you've learnt from your previous projects?
Would you say you quit too early?
Definitely!
You got this! Looking forward to your updates
Thanks a lot. The motivation I'm getting from here is already worth the experiment. 😀
Isn't targeting something to show before the weekend too aggressive?
Yea, it was aggressive, but exactly what I needed to keep the project small. I tend to keep adding features and think the project is never ready for a public release.
I think it's a good idea to keep the projects small(or split them in subprojects) or to release often. I need to work on keeping small the the project(s) I build, as I tend to get lost in details. Building in public is great to keep you focused and accountable. I'm trying to build my current project in public(crossgrowth.io), but I realized I also need to allocate time for building in public and in the same time to limit that time.
You got this bro!
All the best on your new project!
How are you using ChatGPT to keep you on track?
Thanks for the encouragement!
When I fell stuck, I shut a message to ChatGPT and tried to get to a decision ASAP. This didn't happen much this time, as the project is very simple.
But here's an example when I message it about no implementing a feature right now:
Great idea. I have thought of it too. Building a separate smaller part of the main project that usually can't be monetised by itself, but is a great add-on or vital part of the main project. Also, a great opportunity to use it for marketing the main product.
Building something around the main project is certainly great. My problem is always trying to do something completely different.
Great to hear that you're taking steps to address your tendency to start small projects instead of focusing on your main one. Building in public can definitely help with accountability and motivation. Another strategy that may be helpful is breaking down your main project into smaller, more manageable tasks. This can make the project feel less overwhelming and help you make steady progress towards your goal. Additionally, setting specific and achievable goals for each day or week can also provide a sense of accomplishment and keep you on track. Good luck with your new project!
Try to succeed
Looking forward to following here.
What’s your stack?
It's a boring Ruby on Rails application :)
Nothing to scoff at. boring is usually the foundation of most enduring companies.
So true. For instance, I'm seeing a lot of non sense in this AI rush.
@mmaia RoR rocks 😁 (kinda biased here though ahahah)
haha great to know there are more of us out there