DEV Community

Discussion on: 5 Steps to Plan a Side Project

Collapse
christiankozalla profile image
Christian Kozalla

Hey, thanks for these awesome list!

I find myself overthinking Step 2 way to often 😁

I just started a side-project some weeks ago. And it's going to be more complex than what I did before. Frontend + Backend, and I don't have much experience with Node.

So I started with Express, Prisma and Postgres.. I found Prisma and Postgres suitable, but wasn't happy about Express. Then I switched to Hapi and that works great.. So I implemented some routes with Hapi. Now, I've checked out NestJS, which seems to be also interesting, but now that I'm kinda locked in with Hapi, I don't want to switch anymore..

Hapi with Hapi πŸ˜€

Collapse
duy_anh_ngac profile image
Duy Anh Ngac

Hey,

I think it would really help if step 2 and step 3 swap places. That way it is much easier to determine what technology to use, since with features already known a more suitable technology for a job can be found.

Cheers πŸ€—

Collapse
firangizg profile image
Firangiz Ganbarli Author

Hi! For more advanced projects, I guess it is better if their places are swapped. This way works for my side projects, but I guess for more advanced side projects where there are many ways features could be implemented, your way works better. Thanks so much for your insight! ☺️

Collapse
firangizg profile image
Firangiz Ganbarli Author

Hey Christian! Thanks for your comment. Weirdly enough, step 2 usually takes very little time for me to do, but maybe that is because I do not try out different side projects often enough to switch up the technology. Totally understand your viewpoint though. My advice would be to just write a pros and cons list and stick to the result throughout the entire thing. That has worked for me before :)

Collapse
christiankozalla profile image
Christian Kozalla

Thanks for the tips! I'll try my best to do more planning and considerations before coding. Because I know, it'll save me time and struggle down the road πŸ˜€