You're right. The first video was about 5 mins but then I thought I'd add a long video with a good explanation. But initially, I should've done a short demo video to show only the value-added things.
I came here to say just this. When the word "turbo" and phrase "zero distractions" are present, but the demo is a number of minutes long, it feels like something is wrong.
No its not. Its a good video, just bad place for it. I watched it and got to understand your product.
You show the important part in the time frame ~6:00-7:00. Make that part faster and as a gif without sound and the main message is conveyed
> I think we're tired of copying and pasting our codes and sharing links using PasteBin, GithubGist, or Slack.
I think I normally just encourage my coworkers to push the branch (to Github, Gitlab, etc.) to share larger snippets. Smaller stuff, `/snippet` works alright.
But I think the bigger issue with any tool is that corporate isn't going to want company IP uploaded or put into a random website. (This is already the case for a "PasteBin", too; the companies I've worked at wouldn't want me using that, either.) That said, I see this rule violated … a lot. More nowadays with the litany of LLM stuff out there. So, that "self hosted" feature would almost certainly be a requirement, but hosting small tools like this is a high barrier to adoption vs. a process like Slack or Github that has some small friction, but otherwise works.
> Pain points in your current code-sharing process?
Honestly I think the biggest pain point I have with sharing in Slack is that other people don't seem to know how to use Slack. You'll get a code snippet not in a `/snippet`, not even in a code block, just variable-width normal paragraph text.
(The other pain point is that Slack corrupts code-block contents in some cases. ("a known bug here […] currently being investigated by our engineering team […] don't have a timeline for a fix just yet" … the bug has been around for years, so yeah…))
Thank you for your detailed comment and for mentioning the Application Error. Did you land on my page, or was the error blocking it? Please tell me so I can fix that.
You address your thoughts. The snippet folder just works fine, but I was thinking something about real-time, like chatting. I was thinking of making it self-host as an alternative to PasteBin and GithubGist, not only for extensions. But your insight is good. The problem with Slack or Microsoft Teams is the same. People don't even bother to format it; maybe they don't have time to do it. That was the actual pain point for me as well.
Could you tell me more about how I can improve it? Most importantly if it can bring up a better solution compared to Slack, PasteBin, and in-repository "/snippet" folder, would you use it?
I see from your demo that it appears that this is less about just sharing code and more about rapid feedback. Before I watched the video I was wondering how this was different from JetBrains' "Code With Me" or VS Code's "Co-Edit". Might be worth clarifying that it's more than just sharing a snippet in the landing copy.
I agree. For something so "simple", with a name like turbo, I expected a 30 to 60 second video that quickly demos the value-add. I quite like the premise, but you're trying to pitch to users who want low-friction solutions, and then hitting them with a 15 minute video to see the sauce.
Came here to say the same thing. I saw the video was 15 minutes and didn’t even bother. If it takes 15 minutes to demonstrate sharing code, how can it be an improvement over Slack and Pastebin? In the time it takes to watch the video I could have shared so much code on Slack very easily.
Personally, I use pastebin/GitHub Gist because I know it'll be around for a long time compared to all the new ones appearing and I really hate broken links, so my biggest question when coming across this would be "How do they ensure they'll remain online for as long as possible?"
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.
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 :)
I use gist remotes a lot by creating a gist and adding it as a remote to a local git directory.
If i were using your tool, it would be nice to have a single "turbogist" repo for all of the gists. That way i could send gists into it with git push
you could do something clever like this by having turbogist server manage the prefixes , so a git push from any repo would automatically consolidate all of the various prefixes into the turbogist account
Amazing idea!! It starts making me think differently. Thank you so much for sharing this. Could you tell me more about storing and sharing the "gist/pastes" for later use? For example the link validity, or share only with a certain group of people?
gist's "clone with ..." feature is very powerful. It's a unique and (from what I can tell) permanent remote that you can push to. it has some restrictions on naming and file content.
but i would love to see your product run with "clone with..." but make it work for all your experiments
I just wrote up a guide on doing something similar with subtree and a large "experiments" repo .
I share code by pushing it to Github and using the “Copy permalink” functionality from my editor. Then I get a link directly to that commit/line number.
With TurboGist, you don't need to create a Pastebin and paste that link on Slack to send a piece of code. You'll generate a link to add team members to your team, then just share the code with anyone or everyone on your team.
One way is to find at least 5 instances of people complaining about something online using a phrase 'take my money', or 'if only there was a company selling this'.
Seeing this command, I think most of us save more "commands" than "code". In my case, most of them are "commands" rather than "code", because I always forget.
I apologize for the longer video, I should've done a short video rather than explaining the whole thing. Didn't realize it'd impact that much. I can understand your frustration. Give me some hours to make a new one.
I'm sorry, it was my first time creating any product and thinking about SaaS, and I'm still learning it. Please correct me, it'll help me improve and do better.
The "Inline Completion" animation on the home page seems broken. It loops between typing "function" and "function calculate", and the autocomplete code doesn't look like a valid completion for either of those.
Hey everyone, I've trimmed down the video to 55 seconds. Besides, I'll be working on pivoting the idea if needed based on your feedback. Thank you all for your valuable insights.
maybe a bit off topic but as a fellow developer who is working on a project, how did you set up that website? I was thinking of something just like that for my project!
This is cool, but I think my desire to minimize switching focus away from my IDE is outweighed by my need to avoid notifications in my IDE. Ultimately my IDE window is a place for deep focus, and this seems like it detracts from that.
Or maybe this is meant as a replacement for github PRs, meant for async review, in which case I really think PRs work well and don't need to change.
So yeah, I have to agree with others that I'm not really seeing the usecase here
Thank you so much for your detailed feedback. If I cut the vscode extension feature, would you use the other feature which is an alternative to PasteBin or GithubGist?
I think I normally just encourage my coworkers to push the branch (to Github, Gitlab, etc.) to share larger snippets. Smaller stuff, `/snippet` works alright.
But I think the bigger issue with any tool is that corporate isn't going to want company IP uploaded or put into a random website. (This is already the case for a "PasteBin", too; the companies I've worked at wouldn't want me using that, either.) That said, I see this rule violated … a lot. More nowadays with the litany of LLM stuff out there. So, that "self hosted" feature would almost certainly be a requirement, but hosting small tools like this is a high barrier to adoption vs. a process like Slack or Github that has some small friction, but otherwise works.
> Pain points in your current code-sharing process?
Honestly I think the biggest pain point I have with sharing in Slack is that other people don't seem to know how to use Slack. You'll get a code snippet not in a `/snippet`, not even in a code block, just variable-width normal paragraph text.
(The other pain point is that Slack corrupts code-block contents in some cases. ("a known bug here […] currently being investigated by our engineering team […] don't have a timeline for a fix just yet" … the bug has been around for years, so yeah…))
You address your thoughts. The snippet folder just works fine, but I was thinking something about real-time, like chatting. I was thinking of making it self-host as an alternative to PasteBin and GithubGist, not only for extensions. But your insight is good. The problem with Slack or Microsoft Teams is the same. People don't even bother to format it; maybe they don't have time to do it. That was the actual pain point for me as well.
Could you tell me more about how I can improve it? Most importantly if it can bring up a better solution compared to Slack, PasteBin, and in-repository "/snippet" folder, would you use it?
Is this a common feeling? These all work fine for me, what's the issue?
I skimmed through the website, and the only interaction is to join the beta, view a video which is 15mins (too long).
It can be self hosted if you want.
Personally, I use pastebin/GitHub Gist because I know it'll be around for a long time compared to all the new ones appearing and I really hate broken links, so my biggest question when coming across this would be "How do they ensure they'll remain online for as long as possible?"
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 :)
Loved that question!
Yeah, I also think it'd be better to let people use Gist/Pastebin as their backend of choice.
If i were using your tool, it would be nice to have a single "turbogist" repo for all of the gists. That way i could send gists into it with git push
you could do something clever like this by having turbogist server manage the prefixes , so a git push from any repo would automatically consolidate all of the various prefixes into the turbogist account
e.g. https://gist.github.com/tonymet/d5df33b6a5003e1281c458a2d58d...
but i would love to see your product run with "clone with..." but make it work for all your experiments
I just wrote up a guide on doing something similar with subtree and a large "experiments" repo .
https://dev.to/tonymet/how-to-put-everything-in-git-2b3d
you need to distribute the cognitive load on your launch strategy
people cant be invested enough to even answer your actual questions if they're unfamiliar with how you solve their problem
Expiring links might be nice... I have a lot of old gists that don't need to exist, but I'm too lazy to manually delete them.
I don't think such a tool, I would pay for...
I apologize for the longer video, I should've done a short video rather than explaining the whole thing. Didn't realize it'd impact that much. I can understand your frustration. Give me some hours to make a new one.
I'm sorry, it was my first time creating any product and thinking about SaaS, and I'm still learning it. Please correct me, it'll help me improve and do better.
There's also no <title>.
Or maybe this is meant as a replacement for github PRs, meant for async review, in which case I really think PRs work well and don't need to change.
So yeah, I have to agree with others that I'm not really seeing the usecase here