DEV Community

Discussion on: Do this before your next programming project

Collapse
 
jonrandy profile image
Jon Randy 🎖️ • Edited

Why not just make things for fun? A project doesn't have to be useful, a project doesn't have to make money, a project doesn't have a point, a project doesn't have to solve a problem.

Build things because you want to build them.
Build things because you can.
Build things to satisfy your curiosity.
Build things to make art.
Build things organically - don't plan them at all - be creative.

My most enjoyable projects - that I often revisit - are ones that are basically toys... and toys are fun!

This is my latest project. I didn't plan it at all, it was purely driven by curiosity - I just dived in and started playing with ideas. It might be useful to some people, it might not - I don't really care because I enjoyed building it and I find it interesting.

Don't take programming so seriously 😃

Also, believe me when I say that an SRS, UML, all this stuff... it isn't really necessary. I've been a professional developer for 25+ years and have never written an SRS, or used UML. If I have seen an SRS for a project, it's normally something well intentioned that gets written up-front, but 99% of the time ends up languishing somewhere - forgotten about, unused, and unread.

Collapse
 
zairiaimendev profile image
Aimen Zairi

Thank you so much, i actually forgot the most important thing in all of this and that's having fun. Though for that i know that people won't be doing all of these steps. As i specifically mentioned this is if you are serious about a side project or want to make a really big one. Anyway thanks again for the reminder. Fun is truly what keeps me programming but i still find the steps i mentioned as entertaining personally. When i can't think clearly or when i can't explain things by words i always go back and draw diagrams.