Three major updates before the coffee’s done brewing brings to mind a team scrambling to fix a fuck up, fucking up even more, then scrambling to fix that on top of the original fuck up.
“[Dev1]Oooooh sh*t! Prod is down!! AI, we need to fix this ASAP!
-[CodeAssistant] Please wait, I’m working on a solution.
-[Dev1] No, wait! I haven’t given you any details yet!
-[CodeAssistant] Proposed solution: delete entire codebase and database to restart from scratch! Do you want to proceed?
-[Dev2] Mike, do you want to grab a drink after work?
-[Dev1] Yes, sure! … Wait! NOOOOOOOOOOO!”
This all kind of implies that the devs can push to prod whenever they want, which isn’t how everyone else is set up. Some of us want to cordon off all this chaos, just a little, with release windows and scheduled downtime if needed. Which is yet more LinkedIn Lunatic material.
Three major updates before the coffee’s done brewing brings to mind a team scrambling to fix a fuck up, fucking up even more, then scrambling to fix that on top of the original fuck up.
“[Dev1]Oooooh sh*t! Prod is down!! AI, we need to fix this ASAP!
-[CodeAssistant] Please wait, I’m working on a solution.
-[Dev1] No, wait! I haven’t given you any details yet!
-[CodeAssistant] Proposed solution: delete entire codebase and database to restart from scratch! Do you want to proceed?
-[Dev2] Mike, do you want to grab a drink after work?
-[Dev1] Yes, sure! … Wait! NOOOOOOOOOOO!”
This all kind of implies that the devs can push to prod whenever they want, which isn’t how everyone else is set up. Some of us want to cordon off all this chaos, just a little, with release windows and scheduled downtime if needed. Which is yet more LinkedIn Lunatic material.
Well yeah, those three fuckups were the three major updates. Its all about speed with these lunatics
My cortisol!