Comment on Let's blame the dev who pressed "Deploy"
Prox@lemmy.world 3 months agoAre “product” (PM, PO) and “engineering” (people who write the code) one and the same where you work? Or are they separate factions?
Comment on Let's blame the dev who pressed "Deploy"
Prox@lemmy.world 3 months agoAre “product” (PM, PO) and “engineering” (people who write the code) one and the same where you work? Or are they separate factions?
sugar_in_your_tea@sh.itjust.works 3 months ago
No, separate groups. We basically have four separate, less-technical groups that are all involved in some way with the process of releasing stuff, and they all have their own motivations and whatnot:
PM, PO, and QA are involved in feature releases, PM, QA, and support are involved in hotfixes. Each tests in a staging environment before signing off, and tests again just after deploy.
It seems to work pretty well, and as a lead dev, I only need to interact with those groups at release time. If I do my job properly, they’re all happy and releases are smooth (and they usually are). Each group has caught important issues, so I don’t think the redundancy is waste.
My industry has a pretty high cost for bad releases, since a high severity bug could cost customers millions per day, kind of like CrowdStrike, so I must assume they have a similar process for releases.