DEV Community

Discussion on: How to Come Up With Great Side Projects

Collapse
 
pauguillamon profile image
PauGuillamon

I agree in all the points, except for the timebox since most software engineers tend to underestimate (including me) 😂
I have a lot of not finished (and not public) side projects, just a few I have published and my learning is that it's ok to dream big, but be realistic and keep things small. Cutting features is perfectly ok, finish some small projects before doing a big one.

Also work on something you like and find useful yourself, not what someone else told you, and as said in the article, learn tons!

Collapse
 
eekayonline profile image
Edwin Klesman

Totally agree on this part. It is better to pick a small product and go for it with the 80-20 percent rule;

Don't make it perfect, make it work
Don't keep building, start to finish

Obviously, you want something that works, but if the goal is to provide something you actually can make money off, cut out things that you can do manually (ie: forgotten password functionality with <20 users is perfectly doable manually, so scrap those screens).

As soon as you get revenue from customers, improve it and upgrade the experience :)