Recent submissions

Comment · 1 year ago
Couldn't agree more.
Comment · 2 years ago
I agree that the broader software ecosystem has been slow to recognize the importance of Operational Safety. The CrowdStrike outage, while unfortunate, has indeed served as a wake-up call, elevating Operational Safety to a priority for software leaders and CIOs alike.

As you pointed out, the reliance on complex, mission-critical systems is only increasing, and cascading failures are an inherent risk we must address proactively. By learning from organizations like AWS that have successfully integrated Operational Safety into their practices, we can work towards a more resilient and reliable software ecosystem. Let's continue to advocate for making Operational Safety a foundational element in software operations across the industry.

Comment · 2 years ago
Comment · 2 years ago
Couldn't agree more. As someone who used to work at AWS, I've seen it from both sides. AWS has valid reasons (business and technical) for not taking responsibility for all the layers on top. The missing piece is the operational knowledge AWS possesses but platform teams elsewhere lack access to. That's one reason to bring in a “trusted broker” to bridge this gap.
Comment · 2 years ago
k8s complexity is a challenge at scale, but its growth seems likely. Reasons include strong community/support, continuous innovation ensures new capabilities regularly added, overall standardization across various layers of substrate to name a few. It's not for everyone though. Teams with simpler needs might find k8s overkill and opt out for valid reasons. Overall, benefits + community support make it a go-to for many, despite the challenges.
Comment · 3 years ago
What are the factors that lead to ClickOps not scaling? Company size? When should a company know that it’s time to move to IaC?

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton