Hacker News Reader

Comment by daenz | Hacker News Reader

>That is until I realized that it was my own dumb fault because I accidentally left my Plaid environment set to development

One of the last things you do before launch is pay money to yourself by running a real payment with real money in production. An automated test for config is nice, but nothing beats actually doing the critical thing yourself before launching to the world.

View on HN

> which only supported 100 connected accounts. My free test accounts which I had been diligently rationing up until this point had been depleted and Plaid was rightfully denying any new connections.

You picked an odd time to stop reading!

I don't see how this changes anything? If they had attempted to do a production import of their live bank account, it would have been denied, same as what happened to their customers, and they would have caught it before the mistake affected real users.

My understanding was that it would have worked for her because she still would have been under the 100 user limit. So the test env still worked for production data, for the first 100 users.

Yeah, exactly. And running a payment through wouldn't have revealed anything since those two systems aren't connected.

Got it. For some reason, I was reading it as you had depleted the accounts before going live, but that makes much more sense. I take back what I said then about the live production test helping here. Thanks for sharing your experiences!

Au contraire, I was diligently rationing my free test accounts, haha!

Thanks for reading!

Reply on news.ycombinator.com