How One Engineer Recalled a Wrong Production Deploy in 8 Seconds

Failed to add items

Sorry, we are unable to add the item because your shopping cart is already at capacity.

Add to basket failed.

Please try again later

Add to wishlist failed.

Please try again later

Remove from wishlist failed.

Please try again later

Adding to library failed

Please try again

Follow podcast failed

Unfollow podcast failed

How One Engineer Recalled a Wrong Production Deploy in 8 Seconds

Listen for free

View show details

In this episode, Lucas and Luna dive into the story of an engineer at a mid-size SaaS company who accidentally deployed a breaking change to production on a Friday afternoon. Instead of a panicked 20-minute scramble to revert via Git, she had already set up a one-line rollback script — a single shell command that restored the previous deployment image in under 10 seconds. The hosts break down how she built a pre-deployment safety net: an immutable release tag, a pre-push hook that verified the tag existed in the container registry, and a simple 'rollback.sh' that ran 'kubectl set image' from a known-good manifest. They discuss why most teams focus on deployment speed but ignore rollback speed, and how this engineer's approach — treating rollback as a first-class operation — saved her team 40 cumulative hours over the next quarter. Luna questions whether the script could handle database migrations; Lucas explains the pattern of 'expand-contract' migrations that separate schema changes from code deployments. The episode closes on a forward-looking note about chaos engineering and deliberately testing rollback paths. #RollbackScript #ProductionDeploy #IncidentResponse #DevOps #Kubernetes #ShellScripting #EngineeringCulture #SiteReliability #ContinuousDeployment #ImmutableReleases #PrePushHook #DatabaseMigrations #ExpandContract #ChaosEngineering #FexingoBusiness #BusinessPodcast #SoftwareEngineeringPodcast #Technology Keep every episode free: buymeacoffee.com/fexingo

No reviews yet