@[email protected] to [email protected] • 11 months agoWhat's going on y'all?lemmy.worldimagemessage-square93fedilinkarrow-up11.28K
arrow-up11.28KimageWhat's going on y'all?lemmy.world@[email protected] to [email protected] • 11 months agomessage-square93fedilink
minus-square@[email protected]linkfedilink28•11 months agoHow about a testing environment separate from production
minus-squareToes♀linkfedilink11•11 months agoI watched a ocean of computers go dead on the floor because I couldn’t convince the sysadmin to do exactly that when pushing a major change.
minus-square@[email protected]linkfedilinkEnglish3•edit-211 months agoAny more details? This sounds like the setup to a fun story.
minus-square@[email protected]linkfedilink5•11 months agoBest I can do is push it worldwide on a Friday morning
minus-squarepeopleproblemslinkfedilink1•11 months agoYes. And time. We make a lot more money by testing in production, and let the users tell us what’s wrong. It’s much faster.
minus-square@[email protected]linkfedilinkDeutsch3•11 months agoWe’ve successfully replaced the entire support team with an HTML form creating tickets for the one developer. Surefire way to receive that efficiency performance bonus.
How about a testing environment separate from production
and phased rollouts …
And my axe
I watched a ocean of computers go dead on the floor because I couldn’t convince the sysadmin to do exactly that when pushing a major change.
Any more details?
This sounds like the setup to a fun story.
Best I can do is push it worldwide on a Friday morning
Does that cost money?
Yes. And time.
We make a lot more money by testing in production, and let the users tell us what’s wrong. It’s much faster.
We’ve successfully replaced the entire support team with an HTML form creating tickets for the one developer.
Surefire way to receive that efficiency performance bonus.