Why Side Projects Compound 🏗️
For years I treated side projects like a second job I was failing at. 😅 I was still building. The fuel was not a trophy list. It was ideas: problems I could not drop, small "what ifs," things I wa...

Source: DEV Community
For years I treated side projects like a second job I was failing at. 😅 I was still building. The fuel was not a trophy list. It was ideas: problems I could not drop, small "what ifs," things I wanted to exist whether or not anyone asked. Some turned into code and demos. Some stayed half-born in notes. When something did ship, I parked it on Side Projects so I could point back without turning the build into a performance. The hard part was not a lack of sparks. It was guilt. Every hour on a personal repo felt like an hour I stole from rest, from my day job, from whatever version of adulthood the noise online says you should perform. If you have ever closed your laptop at 1 AM 🌙 and thought, this does not count, you know the feeling. Here is the lesson that took me too long to learn: side projects add up over time even when they never become startups. Not because every repo needs a prize. Because they train skills your sprint board rarely optimizes for. ✨ What side projects teach beyo