2 ms·
If the startup isn't costing you a lot it may be best it leave it running. It'll give you more credibility as if someone says "I Made X and failed" yet there's
by brackin 15y ago
If the startup isn't costing you a lot it may be best it leave it running. It'll give you more credibility as if someone says "I Made X and failed" yet there's just an expired domain at X you've basically scrubbed out the past and your work.
There's other sides to this as you won't want an ugly broken site up connected to your name. Case by case basis really.
There isn't a whole lot you could do with the code, i'd just say for most open source it and leave it quietly running, if feasible.
- MrMike 15y agoIt's important to note that it's not just about the financial cost of keeping a service running. For example, I had one service that I built over several months. It got some attention, but ultimately fizzled out. It comfortably lived on some EC2 instances I already had running, sharing resources for the project I had shifted into. However, the support requests came in from the handful of users, and while I wasn't able to make it a financial success, it would've been more of a disservice to those folks to provide a partially functioning, unreliable service rather than give them the chance to migrate away to a competitor that could better serve their needs.