A big CO I work for makes them last only 90 days so you put them somewhere more permanent. There's a gap for the people who can code but don't know how to use the real version control system.

Could you tell me more about the workflow where you worked? Like, how do you guys share code among the team members?

Source control. If it's sharable make it into a real tool and put it in source control. This is what CLIs and libraries are for

Your observation is correct. However, I wanted to have a group of users as beta users to get better engagement. What about you get storage with lifetime access, and the "shared code" will be there as long as you don't delete it?

> What about you get storage with lifetime access, and the "shared code" will be there as long as you don't delete it?

The "lifetime" access is referring to my life, or the life of the service? ;)

Obviously the latter, which in that case, doesn't mean much, unfortunately. I guess I'm at a point where stability is more important than it used to be.

Unless you can find a way of making sure the URLs will continue to work, it'll be a really hard sell until you got a couple years of running the service under the belt.

Or, let people use Gist/Pastebin as the actual backend :)

> The "lifetime" access is referring to my life, or the life of the service? ;)

Loved that question!

Yeah, I also think it'd be better to let people use Gist/Pastebin as their backend of choice.