Surviving the 9 to 5

“Surviving the 9 to 5” isn’t about hustling harder or chasing the next big thing—it’s a raw, no-bull guide for anyone stuck in the daily grind. Each episode delivers real-life hacks to protect your energy, reclaim tiny bursts of sanity, and make it through workday hell without losing yourself. No pep talks. No sugarcoating. Just straight-up survival tips for worn-out souls who refuse to disappear behind their desks.

Surviving the 9 to 5 is a education podcast hosted by Dead Inside by 9:05, with 134 episodes on record and a Required Pod Score of 80. PitchCentric scores this show on Booking Probability, Listen Score, and live audience signals refreshed every 24 hours.

Dead Inside by 9:05 hosts Surviving the 9 to 5, a education show with 134 episodes published.

Our AI reads these to draft pitches. Use them as grounding for a pitch that cites a real guest and a specific topic.

• 

  Surviving the 9 to 5

  Build a No-Code AI Document Reviewer

  Aug 28, 202621 min

  this episode explores the strategic development of an AI-driven quality assurance system for a team handling diverse professional documents.

  ListenShow Notes
• 

  Surviving the 9 to 5

  Briefing: Build a Custom AI Document Reviewer

  Aug 28, 20262 min

  Build a Custom AI Document Reviewer

  ListenShow Notes
• 

  Surviving the 9 to 5

  Copilot Agent File Format Preservation Issue

  Jul 31, 202620 min

  You built a custom Copilot agent at work to translate source files (PowerPoint, Excel, Word, and other supported formats) from Japanese to English. Despite explicitly instructing the agent to preserve the original file format and all formatting/styles in the output, it's either dumping raw translation text into the chat or outputting files with completely broken styling-tiny fonts, ruined layouts, and misaligned elements. What's causing this, and how can you fix it?

  ListenShow Notes
• 

  Surviving the 9 to 5

  Black Duck Polaris for Automated AppSec Governance

  Jul 28, 202626 min

  To understand Black Duck Polaris in the simplest terms, think of it as an automated safety inspector for software. When a company builds an app or a website, Polaris acts like a security guard that checks every "brick and beam" (the code) as it is being put together to ensure the final product is safe from hackers. Technically, it is a cloud-native platform (SaaS) that brings together several heavy-duty security tools into one central dashboard. Instead of using multiple different systems to check for different types of security risks, Polaris acts as a "single pane of glass" where teams can see every potential danger in their software in one place. Polaris performs three main "inspections" to keep software safe: Checking the Blueprints (SAST): It looks at the internal source code for logical flaws (like a door that doesn't lock) without actually running the program. Checking the Materials (SCA): Modern software is mostly built using pre-made "parts" from the internet (open-source code). Polaris scans these parts to make sure they aren't "recalled" due to known security bugs or legal licensing issues. Testing the Finished Building (DAST): It tests the running application from the outside, just like a hacker would, to find weaknesses that only appear when the software is actually in use. Catching "Hidden Keys": It also scans for hardcoded secrets , such as passwords or digital keys that developers might have accidentally left inside the code. While it sounds very technical, it serves several different groups: Developers: They use it as a "spell-checker for security" while they write code so they can fix mistakes immediately. Security Teams: They use the central dashboard to set "safety rules" (policies) and decide which security issues need to be fixed first. Governance & Compliance Leads: These are non-technical professionals (like auditors) who use Polaris to generate reports proving the software meets legal standards (like NIST or ISO) without needing to know how to code. Testing Early ("Shift-Left"): Catching security bugs the moment a developer types them, rather than right before a product launch when it’s more expensive to fix. Supply Chain Safety: Ensuring that any third-party software "parts" the company uses are safe and legally compliant. Automated "Safety Gates": Setting rules that automatically block the release of any software that contains a "Critical" safety violation, ensuring nothing dangerous ever reaches the public. If you were building a house, Polaris is the automated system that checks your blueprints for mistakes, verifies that the lumber you bought isn't rotten, and ensures you haven't left the keys in the front door. It allows companies to build software faster because they aren't stopping for manual inspections—the safety checks are happening automatically in the background.

  ListenShow Notes
• 

  Surviving the 9 to 5

  Black Duck Polaris: Secure Software at AI speed

  Jul 28, 20269 min

  To understand Black Duck Polaris in the simplest terms, think of it as an automated safety inspector for software. When a company builds an app or a website, Polaris acts like a security guard that checks every "brick and beam" (the code) as it is being put together to ensure the final product is safe from hackers. Technically, it is a cloud-native platform (SaaS) that brings together several heavy-duty security tools into one central dashboard. Instead of using multiple different systems to check for different types of security risks, Polaris acts as a "single pane of glass" where teams can see every potential danger in their software in one place. Polaris performs three main "inspections" to keep software safe: Checking the Blueprints (SAST): It looks at the internal source code for logical flaws (like a door that doesn't lock) without actually running the program. Checking the Materials (SCA): Modern software is mostly built using pre-made "parts" from the internet (open-source code). Polaris scans these parts to make sure they aren't "recalled" due to known security bugs or legal licensing issues. Testing the Finished Building (DAST): It tests the running application from the outside, just like a hacker would, to find weaknesses that only appear when the software is actually in use. Catching "Hidden Keys": It also scans for hardcoded secrets , such as passwords or digital keys that developers might have accidentally left inside the code. While it sounds very technical, it serves several different groups: Developers: They use it as a "spell-checker for security" while they write code so they can fix mistakes immediately. Security Teams: They use the central dashboard to set "safety rules" (policies) and decide which security issues need to be fixed first. Governance & Compliance Leads: These are non-technical professionals (like auditors) who use Polaris to generate reports proving the software meets legal standards (like NIST or ISO) without needing to know how to code. Testing Early ("Shift-Left"): Catching security bugs the moment a developer types them, rather than right before a product launch when it’s more expensive to fix. Supply Chain Safety: Ensuring that any third-party software "parts" the company uses are safe and legally compliant. Automated "Safety Gates": Setting rules that automatically block the release of any software that contains a "Critical" safety violation, ensuring nothing dangerous ever reaches the public. If you were building a house, Polaris is the automated system that checks your blueprints for mistakes, verifies that the lumber you bought isn't rotten, and ensures you haven't left the keys in the front door. It allows companies to build software faster because they aren't stopping for manual inspections—the safety checks are happening automatically in the background.

  ListenShow Notes

Based on semantic analysis of episode topics and host coverage, this show is a strong guest fit for executives in:

Industry fit is computed by PitchCentric using vector embeddings of the show's episode catalog.