hastebin Reviews

Substly Reviews

1. Tobias Larsson

   · Business Developer at Founders Loft · almost 3 years ago
   Keeping track of all subscriptions just got (much) easier

   We have a ton of Saas tools. Before using Substly they were scattered around. Now everything is in one place which has made it much easier for us, especially when we are off-boarding someone. Easy to overview and great value for the money.

   👍 Pros:    Easy to use|Great customer support|Great value for the money|Lower cost|Saves a ton of time|Great for collaboration

   👎 Cons:    Slack and teams notification
2. magnus Orrebrant

   · marketing at Svenska Rovdjursföreningen · about 3 years ago
   better control of our saas spending

   Overview - gather everything in one place have improved the visibility of all our subscriptions, quick implementation, improved cost control, User friendly,

   👍 Pros:    Overall quality|Lower cost|Easy user interface|Short learning curve|Overview of cost spend

   👎 Cons:    None
3. Richard Uddh

   · Sales Manager at FlexIT Distribution · about 3 years ago
   Best way to spend money, to save money!

   Using Substly has given us a better understanding of how we use our SaaS-apps and improved our ability to manage software licenses, resulting in better decision-making and cost savings. Substly's overview feature has been particularly helpful in this regard. Additionally, the offboarding feature has streamlined the process of removing software access for departing employees.

hastebin mentions (24)

• node-libcurl vs axios?

  There's a guide on the subreddit wiki on how to format code for display on reddit. When in doubt, you can also use GitHub Gist or Hastebin, though. Source: over 4 years ago

• Problem using Software Serial on ESP32

  In future, use code formatting or put your code into hastebin.com and then post a link here. It will make it easier to read. Source: over 4 years ago

• How do I load cores on RetroArch snap?

  If you want to post a log, you'll have to generate one first (go to settings > logging and set both logging verbosities to 0-debug and 'log to file' to ON, then do whatever you need to do to create the offending behavior; that should make the log. Then, open the resulting log in a text editor and copy/paste the contents somewhere like hastebin.com and post a link to it here). Source: over 4 years ago

• quick qestions

  Close RetroArch, then navigate to your 'logs' folder in your RetroArch user directory (if you can't find it, open RetroArch and go to settings > directory and see where your 'logs' directory is located). You should see a text file there. Copy/paste its contents somewhere like hastebin.com and then post a link to it here and I/we can take a look. Source: over 4 years ago

• x2go cannot find a script in PATH

  Can you give me the entire command history that got you to where you are now? If you can do that, make sure there is not personal information in the history, especially passwords. Look at the output of history. If it's large, try hastebin.com . Source: over 4 years ago

Substly mentions (0)