The hosts share spooky coding horror stories submitted by listeners, including website crashes during a big sale, test messages sent to live Twitter feeds, accidental code alterations, phone number mix-ups, mistakes in production environments, and mistaken money transfers.
Read more
AI Summary
AI Chapters
Episode notes
auto_awesome
Podcast summary created with Snipd AI
Quick takeaways
Always include null checks in JavaScript code to prevent breaking when elements are missing on certain pages.
Be cautious with published content on live websites to avoid embarrassing and irretrievable mistakes.
Deep dives
Failure to Implement Null Checks Leads to Site Breakage
A junior web developer shared their horror story of working on updates for a major furniture retailer's website. Due to their inexperience, they failed to include null checks in the JavaScript code, causing it to break when elements were missing on certain pages. The issue went unnoticed during internal testing, and the code was deployed to production right before the retailer's biggest online sale. Unfortunately, the problem was only discovered on a late Friday afternoon, causing team members to work late to fix the mistake. Although the developer was not directly blamed, they still carry the guilt of causing inconvenience to their colleagues.
Embarrassing Test Page Appears on Twitter Feed
In their early days as a web developer, someone accidentally published a test page on a company's WordPress site. Unbeknownst to them, the site had a live Twitter feed that displayed tweets from the company's account. Consequently, the test message appeared on the feed and was visible to the company's 12,000 followers. Despite promptly deleting the page, the embarrassing tweet remained. They had to seek help from an SEO firm to remove the tweet, highlighting the importance of being cautious with published content.
Mistakenly Disabling Passwords Leads to Security Breach
A lead developer shared their horrifying experience of disabling passwords as part of a feature development process. They forgot to enable passwords again, causing users to log in with incorrect credentials and even access other users' accounts. Investigation revealed that the authentication code had been mistakenly altered. The developer acknowledged their mistake and implemented stricter review protocols to prevent similar oversights in the future. This incident highlighted the significance of thorough testing and avoiding assumptions in coding practices, especially when security is at stake.
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.