Why I lost momentum?

For me building a web-app for a client is way easier than building something I thought of. Because when I start building something I thought of, my head start conversations like:

  • 'Dude you have to use the latest tech stack if you want it to be cool… '
  • 'Dude you have to research this topic thoroughly before you even start…'
  • 'Dude you know what? This idea is better if integrated with/expanded into this other idea…'
The council is on, everyone contributes to the conversation in my head
 

So, from the get-go, there are a number of prerequisites. Once I have spent weeks researching my idea, choosing the latest tech stack, thinking the possible expansion of my idea into an international conglomerate, and spending time checking out other projects, my mind's conversation takes different shape:

  • 'Dude I have to start building this thing now and release an MVP. It has been 3 weeks already…'
  • 'Wow, this latest tech stack I chose seems to have a lot of shortcomings. Check out all these blogs from experts…'
  • 'Who would like my idea anyway? No one even cared to answer my question on HN or IH…'
  • 'Speaking of HN and IH I must spend a lot of time on social media and communities to lay a good foundation for my launch…'
  • 'Have you seen that project on HN anyways? It is almost the same as mine except better…'

Then I usually convince myself to push through and build something, at least a front page. Some kind of landing page for god's sake. At this time, more doubtful thoughts and even shame start creeping into my head. The fact it has taken this long to just build something as simple as this is embarrassing.

To make a long story short I think it is hard for me to work on my ideas because I assume a lot of things that are not necessarily true. On a much more simpler explanation, I think I am just scared to try anything. So I have been taking a safer bet of working on clients jobs. Which is never satisfying but pays the bill.

How I chose to do CodingVideoz

Screenshot of CodingVideoz - a place to find curated videos for developers.
 

I have a ton of ideas that I want to work on. Some of them are very simple like CodingVideoz which is a curated list of best videos for developers suggested by developers. Some are much more complicated. Of all of them, I have finally decided to work on CodingVideoz about 4 months ago. Why 4 months? Please read the previous paragraph. 

Here are some of my reasons for deciding to do CodingVideoz in the first place:

Simplicity

The idea and its implementation can be done so simply. How do I know? I can explain it in a short sentence. 

Itch your own itch. I am solving a problem of my own.

I am 100% sure the problem exists. Why? Because

  • I find myself distracted by YouTube suggestion's storm.
  • I find myself wondering what other developers might be watching.
  • I want to learn without having to do a complete course (burden of commitment).
  • There is so much video out there so I always hoped someone will curate it.
  • Personally, I want to improve and learn continuously. 
  • I want to start something whilst feeding my own curiosity.
  • Reading technical documentation isn't my forte or many other developers.

It is also the problem/need of people I want to relate with and work with i.e developers

How do I know? Because

  • From a number of HN questions, I have learned that people want to watch the best, important coding videos.
  • Developers want to update themselves with the latest change in tech stacks, developers are overwhelmed by the amount of content out there etc.
  • Developers don't want to waste time watching every video, and now our community can select the few must watch ones.

How I decided to launch it even if I have lost momentum

When I returned from some client works into CVZ I was dejected about the idea and my draft work. But I finally realized I need to treat my side project just like a client project. 

Normally, on a client job, I discuss with the client about what they need, and I try to deliver as fast as possible. No back and forth, at least in my head. No obsessing about tech stack. No worrying about if I will ever make money, etc. It is even simpler if the client knows what they want and when they want it.

In this case, the client is me and hopefully some other developers. Hence I forced myself into posting what I have done so far on this subreddit - To start the conversation. The product was at a very early stage, almost just like the initial draft I would send a normal client. And I got lucky because subreddit reacted vocally just like my clients do on my post.

From one annoying client to thousands of different voices

It was shameful but at the same time a thrilling experience. It was shameful because some members of the community criticized how the site is not done right. But wait a minute, wouldn't a client do the same? Yes, they would. It was so surprising because the community took the idea well, and I saw some encouraging signs to take things where I left off. 

Within 12 hours of me posting the site on /r/learnprogrammin 2k people visited it and almost 100 programmers subscribed. 

Google analytics overview after 12 hours of posting my site on reddit
1

Fired up again

Yesterday, I was so fired up to see all that reaction on Reddit, and to learn how people cared about what I want to build. Now I have thousands of developers, who are willing to try it and are waiting for my site to be less messy. This is it. Now I am on a path. I am not alone. I have people who complain, criticize, encourage and support me. I even have some copycats already :)

This is the best feeling there is and as we are all emotional beings, it is what moves us to do something. This is the reason I am fired up again. So my take away from this experience, find your client on the first day and work with them. Illicit some emotion in them and in you. Treat your side project just like another client project.

    More from Indie Hackers: