Work hands you the problem. Side builds train choosing, cutting scope, and shipping when nothing is spelled out. Your own deploy surprises make work incidents feel familiar. 🧠
AI didn’t delete the work. It moved the bottleneck up the stack. ⚡ The scarce part isn’t faster typing. It’s naming the problem, picking limits, and knowing what good enough means for a real user. 🎯
Full blog 🔗: souravdey.space/blogs/why-side-projects-compound
📣 Share a side project you’re proud of in the comments. 💬
#SideProjects #SoftwareEngineering #DevDecodedWithSD
james
Strong point side projects really sharpen decision making under uncertainty. I’ve been experimenting with a small puzzle related tool recently, where the real challenge wasn’t coding but defining “good enough” for users and keeping the scope tight. It’s interesting how quickly you run into real world tradeoffs. If anyone’s curious about that kind of build, here’s one example I explored: Block Blastsolver tool simple idea, but a lot of thinking behind usability and outcomes.
Would love to see what others are building too 👀