4 ms·
Like setting up rules enforcing pull requests to merge to production branch and having all PR needed to be reviewed by at least 2 ppl with no escape mechanism i
by havkom 5y ago
Like setting up rules enforcing pull requests to merge to production branch and having all PR needed to be reviewed by at least 2 ppl with no escape mechanism in place..
Great until something goes terrible wrong and some absolute critical bug has to be fixed when you are on-call alone on a weekend.
Never disallow escape hatches. You may not need both your arms in your everyday job or in your life in the ideal case, but keep cool and wait going to the doctor for an amputation just in case.
- Tade0 5y ago> Great until something goes terrible wrong Or when you have four team members, but one is on vacation and another called in sick today.
- Vinnl 5y agoAnd the flipside is: don't abuse escape hatches.
- bluGill 5y agoDepends on your domain. I'm in embedded systems, with some safety critical parts. It costs millions of dollars to upgrade production after the release is done - we are not interested in your weekend fix, it better be right in the first place, or it is millions more to deploy the next update. That we are safety critical means that we wouldn't release anyway as we don't dare risk your change resulting in some worse safety issue than the one you are trying to fix. The minimum time for a critical fix to make it into production is 6 weeks of tests. (Yes we have extensive automated tests, they still don't catch everything - as anyone use uses the popular web platforms that release to production often has figured out)