CI/CD Pipeline from Hell

CI/CD PIPELINE TEST BUILD DEPLOY DEV MANUAL TWEAKS FORGET ABOUT THE TWEAKS DEPLOY STAGING NOTHING WORKS MORE TWEAKS WAIT FOR CHANGE APPROVAL HEAT DEATH OF UNIVERSE ESCALATE TO DIRECTOR CHANGE APPROVED SIGHT-UNSEEN WAIT FOR 3AM MAINTENANCE WINDOW DEPLOY TO PROD EVERYTHING WORKS! JUST KIDDING. WHY WOULD ANY OF THIS WORK ERRORS DOWNTIME PANIC 50-PERSON CONFERENCE CALL MANY MANY MANUAL TWEAKS PROD RETURNS TO AN ACCEPTABLY BROKEN STATE ADD LINKEDIN SKILLS: DEVOPS, AUTOMATION, TROUBLESHOOTING

A hand-drawn flowchart shows a CI/CD pipeline spiraling from testing and building into manual tweaks, broken deployments, approvals, late-night maintenance, downtime, panic, and a huge conference call. The punchline is that production never becomes truly reliable; the ordeal merely ends in an “acceptably broken state,” while the whole chaotic process is ironically presented as LinkedIn skills. It is sent as a reaction to painful software releases, overcomplicated DevOps processes, and organizations that rely on manual fixes. EN: A hand-drawn flowchart shows a CI/CD pipeline spiraling from testing and building into manual tweaks, broken deployments, approvals, late-night maintenance, downtime, panic, and a huge conference call. The punchline is that production never becomes truly reliable; the ordeal merely ends in an “acceptably broken state,” while the whole chaotic process is ironically presented as LinkedIn skills. It is sent as a reaction to painful software releases, overcomplicated DevOps processes, and organizations that rely on manual fixes.

• @right_wing_dev_squads / 4569 2022-08-01