News for hackers. Stuff that matters.
Re:Shutting Down a Dream by dquail on Thursday August 08, 2013 @01:56AM (#6177527)
I buy it. It's never that clean.
Re:Shutting Down a Dream by prawn on Thursday August 08, 2013 @02:31AM (#6177618)
They're not saying that it's clean, but that it beats throwing something away.
Re:Shutting Down a Dream by dquail on Thursday August 08, 2013 @03:09AM (#6177679)
I guess that's my point though. That "throwing it away" makes you completely unencumbered. There's value in that. Anything else comes with strings that make it really hard to move on ... even if that's emotionally.
Re:Shutting Down a Dream by prawn on Thursday August 08, 2013 @07:12AM (#6178215)
Then you hand it over, embarrassing warts and all, zero documentation, and walk away.

I think we throw away too much.

Whatever is wrong with it, this could be a good start for someone without their own project or inspiration.

Re:Shutting Down a Dream by ProblemFactory on Thursday August 08, 2013 @08:45AM (#6178522)
I can't speak on behalf of the author, but I have been "stuck" in similar limbo projects myself (an iOS game).

Admitting to yourself that the project has failed, and "just one more push" can't rescue it, and shutting it down is emotionally difficult enough. Handing it over involves finding a suitable recipient, instructing them, transferring domains and accounts, and making sure the clients understand the ownership has changed. And refusing to answer requests for help or documentation over email can be impossible, especially if you cared about the project or its users. Without this documentation and knowledge, a code repository is of almost no use to anyone.

If someone is capable of walking away with zero documentation or help, they would have shut down a limbo project much earlier.