News for hackers. Stuff that matters.
Re:Software developer's guide to release a side project: Par... by codingdave on Saturday January 03, 2015 @01:02PM (#8831425)
Side projects for me are weekend projects. I toss them onto my personal site and watch it for a few months to see if it gets used and if I get any feedback. If it does, I'll polish it some more and try to do something with it.

But I'm not going to go make up branding, set up a new domain, and build a bunch of marketing when I don't even know if the project works for people or not.

So in my mind, Part 1 of releasing a side project is: Have a personal site with enough traffic to act as a testing ground for your ideas.

Re:Software developer's guide to release a side project: Par... by melvinmt on Saturday January 03, 2015 @01:37PM (#8831551)
If your side project lingers on your personal site where nobody sees it, how would you ever know if people need what you're making? This is the typical "if I build it they'll come" pitfall.

You're basically talking about validating your idea before you spend any more time on it but if you truly care about validation, it's actually the opposite: you'll need to spend more time to validate your idea.

Re:Software developer's guide to release a side project: Par... by codingdave on Saturday January 03, 2015 @02:26PM (#8831701)
Your assumptions about my motivation are incorrect -- I need what I am making. That is why I make things. If other people also like it, then I turn it into something more. Sometimes.

It has built up into a little site with a few thousands users each month. Which I know is small potatoes to a lot of people, and doesn't hold a candle to my actual job. But it is plenty for me.