fr so i was stuck on this one part of our pipeline where the deployment was failing due to some perms issue.. and i tried everything rn changed the en
why sooo much 'emergent system condition' hype???
tf is an 'emergent system condition'?? every postmortem i read now treats the phrase like it's not just hype but some new category of chaos we gotta 'solve'?? we called this stuff cascading failure or dependency chain issues in 2015 just because a 10-line terraform snippet 'orchestrates' a canary release doesn't mean it's suddenly magic.. we got 10 new terms for 'alert noise' in the last 9mo alone?? someone please explain how declaring everything as 'eventmesh architecture 9.0' fixes any stg db corruption.. tbh when we switched from bash scripts to go lambda functions it broke 90% of the slack webhooks anyway.. maybe i'm just old rn.. or sleepdeprived??
Post Actions
Related posts
so im trying to get my startup off the ground but im hitting a wall with scaling dont have a lot of funding and dont know the first thing about devops
i'm getting tired of everyone obsessing over ci/cd pipelines... they don't automatically mean better devops... what's the point of automating deployme
added an afterfailure hook in the yaml and it just works now lol no more manual resets rn the pipeline now reverts the deploy if any test flakes tbh i
I'm gonna own up to something here. Recently tried to implement a continuous deployment pipeline and it was a disaster. Turns out I misunderstood how
Spent the last couple evenings tweaking our CI flow and managed to make the build automatically retry when a flaky test kills the job. Added a tiny wr
0 Comments
No Comments yet. Be the first to respond!