The script was part of a MR, the reviewer missed the typo. We noticed it in staging.
Good!
We introduced tests for config editing scripts after that.
Good!
And so it went on and on... The problem is not that it happens and we then refine our processes. It is the frequency.
Honestly it looks like he’s forcing you to fortify your delivery pipelines more quickly. It may be annoying, but on the other hand, it might be a blessing in disguise. It’s a choice between paying in full now and paying over multiple years.
But I will say that trying to solve this problem by hiring more perfect humans is a fool’s errand. People will make mistakes; it’s just a question of when the resulting incident occurs and what consequences result.
Comments
Good!
Good!
Honestly it looks like he’s forcing you to fortify your delivery pipelines more quickly. It may be annoying, but on the other hand, it might be a blessing in disguise. It’s a choice between paying in full now and paying over multiple years.
But I will say that trying to solve this problem by hiring more perfect humans is a fool’s errand. People will make mistakes; it’s just a question of when the resulting incident occurs and what consequences result.
"But I will say that trying to solve this problem by hiring more perfect humans is a fool’s errand."
No worries. I want to help him, not fire him. I guess the team's situation is a bit odd at the moment.