2 ms·
Once worked for a company that had a subscription based service. They wanted a monthly report of expired accounts so that they could warm-call for renewals. T
by tracker1 8y ago
Once worked for a company that had a subscription based service. They wanted a monthly report of expired accounts so that they could warm-call for renewals. The bug was that some accounts had paid for 2 years. After a couple years, someone noticed that the reports hadn't been including the 2-years subscriptions and it was effectively a loss of a couple million in revenue.
While I did code it to the specifications I was given, and was really clear on understanding it was still a pretty big failure.
-----
Second biggest failure was checking in the db connection against a production database into source control. It was internal source control, and the transforms (ASP.Net Web.config transforms) had it anyway, so wasn't an increased risk in that regard. I was troubleshooting a production issue.
What happened is another developer had used that connection configuration to drop/recreate a table. It took a few hours to recover from (DB restore, then replay against API activity logs). And a day of lost time for a few hundred workers.