Live data from Hacker News

SaaS We Happily Pay For

francescodilorenzo.com

171–180 of 229 posts

Re: SaaS We Happily Pay For

#171
post #52

If you go to that Linear one’s site on an iPhone and zoom in really fast on their image of the todo list client, it immediately restarts your phone.

I reproduced it to happen with just the animated glow behind the todo list. Zooming in and then out to this animation throws my 14.2 XS Max to the lock screen.

https://codepen.io/maybevain/pen/mdrpPEg

Re: SaaS We Happily Pay For

#172
post #91
post #53

> We pay for this, even if we are the ones making it, to test our Stripe Integration. This is so important! This can go wrong even at large companies. At Netflix we once had a billing issue and it took a while to even notice, because no one in the company was paying for it (it was just free for everyone), but it looked like just general attrition, not people slowly having failed payments. After that incident, the com…

Actually technically this is prohibited by stripe. They explicitly ban testing your app in production. We have offered suggestions many times to them, but still no feature here.

Even with a personal checking account/card? This is unfortunate to hear...

Re: SaaS We Happily Pay For

#173
post #165

Earlier quoted context omitted.

It's the way the credit system was designed, even before widespread computer networking - based entirely on trust. The customer would bring the card in and the merchant would make a signed carbon copy and call it in or deliver the receipts to the bank every day, which would settle the accounts between banks over a week or so, with the credit card provider carrying some level of liability. This is one of the reasons c…

Presumably, somewhere within the bowels of American Express, there's a test card for testing the Centurion large-payment verification process, where feeding it through a merchant and having them run a verification on it, will get them routed to a mock concierge on Amex's side (or rather, a human concierge diverted to follow a special mock workflow script.)

"Everytime you run your test suite, someone actually gets up for every test case, runs over to the copy machine, and creates physical carbon copies for DHS."

Re: SaaS We Happily Pay For

#174
post #9

While I think it's great you're thinking of tools to optimize your time BUT a team of 3 at early stage project/startup level should be a bit more frugal and look for clever ways to save the ~$200/month you're spending right now! I understand you have your own SAAS and want to justify subscription and this is a good promo method. I've written on HN before that I'm TIRED of subscription apps, specially per user subs, f…

Vercel billing per-user is so head-scratching. I think it's a greedy billing strategy.

I would switch to Cloudflare Pages for a serverless setup.

Re: SaaS We Happily Pay For

#175
post #168

Earlier quoted context omitted.

Do you think FOSS stacks are made of ice? That they would melt if you don't constantly resupply fresh ice from arctic excursions. Surely you maintain your start-up tech on F/OSS, as most of the internet does, so just use the person who types 'apt-get update && apt-get upgrade' on your service to do the same on your local VM. Or leave keep it local and literally never update it. It wont melt.

> Do you think FOSS stacks are made of ice? That they would melt if you don't constantly resupply fresh ice from arctic excursions. Yes, if you care about things like not getting oWn3d and having your customer data exposed.

> Or leave keep it local and literally never update it.

The mouth salivates at this prospect.

Yes, please set up your Jenkins server once and never look at it again...

Re: SaaS We Happily Pay For

#178

Earlier quoted context omitted.

Most importantly it gets you SSO on basic plans for any SaaS. Big companies using Okta or something have to pay for all those Enterprise plans just for that.

> Most importantly it gets you SSO on basic plans for any SaaS. Is that because most SaaS offers "sign in with google"? Or is there something else involved?

Yep, saves a lot of annoyance having to keep track of a bunch of logins across SaaSs especially when you need to revoke access when someone leaves, so instead of having to go to all the various services individually to deactivate the accounts, you can just deactivate their Google account or revoke its access to those services.

Re: SaaS We Happily Pay For

#179
post #21

Earlier quoted context omitted.

Right. $27/month per user for email filtering and meeting scheduling seems absolutely crazy. While I applied the idea of supporting other small startups, lots of the items in this list seem frivolous!

> $27/month per user How does this even matter from a budget perspective? You are already paying probably in the $10-20k / month range for per-employee salary. Seems a lot like complaining about a dripping faucet while you have a water main break.

Because you can only play the "this is trivial compared to the employee's salary" card so many times before the numbers add up to a nontrivial sum.

Re: SaaS We Happily Pay For

#180
post #147

Earlier quoted context omitted.

I'm surprised the payment system is designed in such a way to make that possible

It's the way the credit system was designed, even before widespread computer networking - based entirely on trust. The customer would bring the card in and the merchant would make a signed carbon copy and call it in or deliver the receipts to the bank every day, which would settle the accounts between banks over a week or so, with the credit card provider carrying some level of liability. This is one of the reasons c…

They should have mock Lamborghini dealerships and mock supercar test-drives so any developers debugging can be confident of all their changes.
Post reply on HN