News for hackers. Stuff that matters.
Re:Gobble Promises to Help Customers Make Delicious Meals in... by Swizec on Wednesday September 24, 2014 @02:03PM (#8363026)
I've written bugs like that before.

You never think "Do X every week" is going to be difficult to code, but man, when I actually coded that ... a lot of things can go wrong in subtle ways that you don't really consider in advance until a customer clicks something or uses features in a sequence nobody's ever stumbled onto before.

As for the credit card thing - easily explained as "Submitted info to Stripe, but not the actual form, backend system got confused"

MVP LYFE!

Disclaimer: I never worked at Gobble, I don't know if this is what's happening, but I painfully know how this can happen

Re:Gobble Promises to Help Customers Make Delicious Meals in... by UrMomReadsHN on Wednesday September 24, 2014 @02:34PM (#8363236)
> don't really consider in advance

Someone abandoning the checkout process is absolutely the first thing you should consider in advance.

Re:Gobble Promises to Help Customers Make Delicious Meals in... by Swizec on Wednesday September 24, 2014 @02:43PM (#8363302)
Emphasis on should.

There's a lot of things you should do, but the truth is that making modern async webapps with a million moving parts is hard.

Re:Gobble Promises to Help Customers Make Delicious Meals in... by UrMomReadsHN on Thursday September 25, 2014 @11:35AM (#8367659)
I've build web applications of all different sizes from the pretty simple to the really friggin complex (and I'm talking really really complex, not just some damn reoccurring food order). I'm more than familiar with it.

If you are doing something so brain dead as charging customers who abandon the checkout process that means there is a huge problem with how you are running your shop. When you charge a CC you have to make absolutely SURE you get permission first, that's like really important. From a moral standpoint, a legal standpoint, and a "I want to keep my agreements with MasterCard/Visa/etc" standpoint.

Re:Gobble Promises to Help Customers Make Delicious Meals in... by protonfish on Wednesday September 24, 2014 @04:16PM (#8363858)
For some reason I can't replay to your other comment. Weird.

I build modern async web apps for a living and it's not that hard. I ran eCommerce for a medium-size software company (as a part of my duties) for several years. If you find an ecommerce application difficult to maintain, it is probably a result of poor design.

Re:Gobble Promises to Help Customers Make Delicious Meals in... by Swizec on Wednesday September 24, 2014 @04:58PM (#8364098)
I too build modern async web apps for a living and I think anyone who says it's not hard (or at least complex) is either lying or in denial.

And there's eCommerce and then there's eCommerce. Recurring weekly subscriptions with moving parts are hard. Amazon Subscribe&Save is a mess and I haven't heard of anyone who's had a good experience with that. And Amazon probably devoted much more engineering power to that problem than people at a startup can.

Sometimes hardness isn't a result of poor design, but the result of things being complex. Especially if (as in a startup) your definition of "things" is changing rapidly because you're still not sure what exactly you are building.

Re:Gobble Promises to Help Customers Make Delicious Meals in... by DanBC on Wednesday September 24, 2014 @04:24PM (#8363914)
> For some reason I can't replay to your other comment. Weird.

HN has built in rate-limiting. Sometimes you have to wait for the reply button to show.

Re:Gobble Promises to Help Customers Make Delicious Meals in... by protonfish on Wednesday September 24, 2014 @03:58PM (#8363746)
I'm sorry but eCommerce isn't rocket science and neither is proper QA.
Re:Gobble Promises to Help Customers Make Delicious Meals in... by Swizec on Wednesday September 24, 2014 @04:05PM (#8363794)
Which is why companies with thousands of employees and a bunch of money launch buggy products to the market every day and scrappy startups shouldn't. Right?