Read a post related to zepto tech on grapevine and ended up going through their blogpost

So user @fiercyfirefox made a post discussing if zepto tech is good or bad (https://www.grapevine.in/post/zepto-tech-is-facing-really-bad-tech-debt-203ac312-9aa3-45dd-bb26-7eeab2c9c533)

Somehow ended up at their blogpost and immediately the second article caught my eye ( https://blog.zeptonow.com/everything-was-fine-until-kubernetes-said-no-more-cpu-3768cda76326 ). Now I'm kinda sus about how good are their engineering practices. Not throwing shades or anything, just want folks to weigh in their thoughts

(I understand that when things are going at breakneck pace and high burn, good practices must take the backseat and just getting things to launch take the front seat; however after a while certain guardrails should be setup to allow high velocity without having high fatality)

(The issue they faced is something that uber already faced and wrote a blog about, along with their own tooling -> https://github.com/uber-go/automaxprocs) (and also a few months back someone had posted a similar issue on r/golang)