The post argues AI-written incident reviews fail without rich cross-system data and human engagement because incident reviews are socio-technical learning work, not just document generation.

The post walks through ten status page examples and highlights clear communication, simple layouts, and expectation-setting details that help users during incidents.

The post argues teams should make reliability targets, support limits, and roadmap uncertainty explicit early so customers and stakeholders do not build riskier implicit expectations.

Five practical DX improvements for daily OpenTofu/Terraform + AWS work: use `tenv` for seamless version switching, a `grep` alias to summarize plans quickly, `tflint` with cloud provider plugins for linting, `awsp` for fast AWS profile switching, and a customized shell prompt showing the current branch/workspace/profile at a glance to prevent costly wrong-context mistakes.

A zero-cost drift detection pipeline built entirely on GitHub Actions uses Terraform's native `-detailed-exitcode` flag to auto-discover root modules, run daily parallel plans, and open GitHub Issues when drift is detected — no external tools or paid services required, with OIDC for keyless AWS auth.

An open-source platform from Electrolux that lets platform teams define reusable Terraform templates while enabling developers to self-serve multi-cloud infrastructure (AWS, Azure, GCP) via pull-request-driven continuous delivery, with audit logging and an MCP server for AI agent integration.

AI agents get filesystem access, run shell commands, and are wide open to prompt injections. The standard response is guardrails and policies. The problem is that policies can be bypassed — and guardrails can be talked out of.

With nono, you don't have to. nono wraps your agent in a kernel-isolated sandbox in seconds — with API key protection, destructive action guardrails, and full snapshot/rollback built in. No hypervisor to configure. No container volume mounts, instead fine grained capability control to the file level. Zero latency overhead.

A fast package manager for macOS and Linux. Written in Zig. Uses Homebrew's bottles and formulas under the hood, plus native .deb support for Docker containers.

In 2024, the Online Data Stores team at Netflix conducted a comprehensive review of the relational database technologies used across the company. This evaluation examined functionality, performance, and total cost of ownership across our database ecosystem. Based on this analysis, we decided to standardize on Amazon Aurora PostgreSQL as the primary relational database offering for Netflix teams.

How Airbnb ships dynamic config changes safely and reliably.

Docker builds taking forever? I cut mine from 8 min to 24 sec. Here's how using Buildx and caching.

In this blog post, we will explore Terraform parallelism: what it is, how to manage it, and best practices for configuring parallelism in Terraform.

Terraform is the most popular solution for implementing Infrastructure As Code (IaC). The Terraform provider registry contains a very large collection of providers/integrations for all the major cloud providers and at the same time offers a wealth of integration for databases, networking components, Continuous Integration platforms etc.

Argo CD is the leading solution for GitOps deployments on Kubernetes. In the last CNCF survey we found out that 60% of respondents use Argo CD in production.

Although several guides currently exist that explain how to use each tool individually, there is limited information on how they can be combined. A lot of existing Terraform users adopt Argo CD and wonder:

1. What is the best way to pass variables from Terraform to Helm charts deployed with Terraform?
2. How to get secrets in Kubernetes applications that are generated/retrieved from Terraform?
3. When should the Terraform Helm and Kubernetes providers come into play if Argo CD already supports Kubernetes deployments on its own?
4. For which Kubernetes resources should Terraform be responsible and for which Argo CD?
5. What is the proper boundary between the two tools so that operators can use them to the maximum benefit?

In this guide, we will answer all these questions and actually show you four different approaches for how Terraform and Argo CD can work together. Note that everything we say about Terraform also applies to OpenTofu.

This database cluster contains most of Etsy's online data and is made up of ~1,000 tables distributed across ~1,000 shards.

AI collapsed the cost of building software, but the systems underneath are buckling.

It took us 4–5 incidents over several weeks to even recognise the pattern.

All those systems were air-gapped, meaning the team that builds the software has no access to metrics, logs or runtime.

From the inside, it was a systems failure spread across FastAPI, uvicorn, Redis, ClickHouse, APScheduler, Docker memory limits, and a startup sequence that had quietly become a deterministic self-attack.

There is a distinct, visceral kind of pain in watching an otherwise brilliant engineer hold down the Backspace key for six continuous seconds to fix a typo at the beginning of a line.

We’ve all been there. We learn ls, cd, and grep, and then we sort of… stop. The terminal becomes a place we live in-but we rarely bother to arrange the furniture. We accept that certain tasks take forty keystrokes, completely unaware that the shell authors solved our exact frustration sometime in 1989.

Here are some tricks that aren’t exactly secret, but aren’t always taught either. To keep the peace in our extended Unix family, I’ve split these into two camps: the universal tricks that work on almost any POSIX-ish shell (like sh on FreeBSD or ksh on OpenBSD), and the quality-of-life additions specific to interactive shells like Bash or Zsh.