2 ms·
But it’s also common to stick those flags back under some sort of audit system so we know why and how weird states got set. The simplest way is a separate repo
by hinkley 2y ago
But it’s also common to stick those flags back under some sort of audit system so we know why and how weird states got set. The simplest way is a separate repo with simpler rules for pushing to master.
Though you could also create your own audit system (just make sure it functions even when the entire site is down)
- bottd 2y agoThis is all decided by business needs, not by engineer preference. If devs aren’t pulling the levers it is good to expose them in an accessible interface, not plaintext.
- hinkley 2y agoLet’s not pretend like these “business needs” don’t often boil down to a couple of tropes and that the story doesn’t change after a couple of post mortems are turned in for perfectly predictable failure modes.