In this chapter, the speaker shares two spooky coding horror stories. The first story involves accidentally sending a test message to a live Twitter feed, and the second story is about a developer mistakenly altering the authentication code. The chapter discusses the consequences of these incidents and the measures taken to prevent similar oversights in the future.
In this Hasty Treat, Scott and Wes relate some spooky listener submitted coding horrors including updates for a large furniture retailer, pull request oversights, disallowing everything in a robots.txt, massive email fail, and more.
Show Notes
- 00:21 Welcome
- 01:22 Whetting your whistle
- 01:52 Syntax Brought to you by Sentry
- 02:13 Site updates for one of the largest furniture retailers in my country
- 04:18 The Embarrassing Test Page Incident
- 05:54 The Pull Request Oversight
- 08:02 Making changes to a JSON file
- 13:11 Deploying a “disallow everything” robots.txt
- 14:45 GDPR Deletion
- 16:11 Dropping the backing disk for the production postgres
- 17:05 Accidentally pushing staging code as an update
- 18:34 Email fail
- 19:25 Hot mobile app prayers
- 22:28 Bogus ACH info
- 23:51 Wiring money error
- 26:44 Payment gateway test not production
Tweet us your tasty treats