As a follow-up to our last post, we went deeper into how teams are actually trying to standardize their engineering practices at scale. Here’s what we saw: • CI templates sound great in theory with best practices baked in. But in reality we heard lots of “this doesn’t fit our use case” stories, legacy services that never switch, and teams quietly opting out. • Manual production-readiness checklists decay into box-ticking fast especially when teams are under pressure to deliver. • Scorecards provide some visibility, but often surface shallow signals and are rarely checked by developers directly. • Vendor tools go deep in specific areas, but because the information is scattered it’s hard to understand the bigger picture. Would love to hear how others are tackling this - what’s actually worked for your team?

Can you please elaborate more on this? What are the tools being used and their purpose, and what are the gaps you are observing? Couple of real life examples? Regards

We were primarily interested in understanding how teams standardize on quality, security, compliance. There’s some better examples in the article if you’re interested in taking a look: https://earthly.dev/blog/slack-archived-service-running/