Your Job & Career
The newsletters every DevOps and site reliability engineer should be reading
Four sources on reliability, incidents and cloud, read to you as one short briefing, so you learn from other people's outages instead of only your own.
The best newsletters for DevOps and site reliability engineers right now are DevOps WeeklySRE Weekly, and TLDR Dev. Below is our full 4-newsletter reading list for the role, each one verified against its live signup page, with why it earns a slot, and available as one five-minute daily audio briefing.
The bundle at a glance
| # | Newsletter | Cadence | Cost | Readers | Best for |
|---|---|---|---|---|---|
| 1 | DevOps Weekly | Weekly | Free | ||
| 2 | SRE Weekly | Weekly | Free | ||
| 3 | TLDR Dev | Daily | Free | 470k readers | |
| 4 | Last Week in AWS | Weekly | Free |
Why niche newsletters, not the same news everyone reads
This field documents its own failures in public, and that literature is scattered across engineering blogs, incident reports and conference talks. Curated weeklies are how practitioners actually find it. General tech coverage reports that a service went down; the reliability newsletters tell you the mechanism, which is the only part that transfers to your own system. The cloud providers also ship changes faster than any team can track, so an editorial filter on that flow is worth real money.
What the job really takes
Reliability work is the job of keeping a system honest under load, change and failure. You are building the paths that let other engineers ship safely, then owning what happens at three in the morning when something they shipped meets reality. The day is a mix of platform work, automation, capacity and cost, punctuated by incidents that demand a calm sequence of diagnosis, mitigation and an honest write-up. The hardest parts are rarely technical alone: they are about blast radius, error budgets, and how much risk an organization has actually agreed to carry.
How to stand out
The engineers who become the person others want on call are the ones with a deep library of other people's failures. Postmortems are the field's shared literature, and reading them teaches you the failure modes you have not personally survived yet: the retry storm, the certificate nobody owned, the dependency that was fine until it was regional. That reading is also what lets you argue for reliability work in terms a business understands, which is the difference between a platform team that gets funded and one that gets absorbed.
Where this bundle comes from
Every newsletter in your bundle comes from the category that matters most in this job:
- 4Software Engineering →Reliability and platform work is catalogued inside the software engineering press: the curated weeklies for incidents and practice, and a daily wire for the tooling and cloud changes underneath.
Your 4-newsletter bundle
- 1
Why devops and site reliability engineers read itGareth Rushgrove's curated weekly, running since 2010, on the tools, practices and writing worth your attention. Longevity matters in a field full of vendor noise: this is a human filter with fifteen years of taste behind it.
Each week Rushgrove — a veteran of Puppet, Docker, and Snyk — sends a plain list of the DevOps articles, tools, and talks he found most interesting, spanning infrastructure automation, delivery pipelines, and operations culture. One of the oldest continuously running newsletters in the space. Free, delivered via Mailchimp.
- 2
Why devops and site reliability engineers read itLex Neva's weekly on availability, incident response, human factors and automation, curated since 2015. It is the best single route to other people's postmortems, which is the fastest way to learn failure modes you have not lived through.
Weekly links with commentary covering everything related to keeping services available: incident write-ups, resilience engineering, observability, databases, Kubernetes, and human factors. Neva is a staff SRE (Honeycomb, previously Fastly, Heroku, and Linden Lab) and has published 500+ issues over roughly a decade. Free, with email, RSS, and Mastodon delivery.
- 3
Why devops and site reliability engineers read itA daily five-minute read of engineering news, tools and links for roughly 470,000 developers. The weeklies give you depth, this gives you the clock, so a major release or a serious vulnerability does not wait for the weekend.
TLDR Dev is the software engineering edition of the TLDR network: one daily email of programming news, new tools, and web development links, each with a one-paragraph summary. It is aggregation, not commentary, tuned for working developers across the stack. Best for engineers who want the day's dev news skimmed in five minutes.
- 4
Why devops and site reliability engineers read itCorey Quinn's weekly round-up of AWS announcements and cloud-industry news, written by a cloud economist with an eye for what a change actually costs. It is the rare source that treats cloud spend as an engineering concern rather than a finance one.
A weekly digest of AWS news, releases, and security items with Quinn's trademark sarcastic commentary — the pitch is taming the 'drinking from a firehose' pace of AWS announcements. Quinn is Chief Cloud Economist at The Duckbill Group, an AWS cost-optimization consultancy, and also hosts the AWS Morning Brief and Screaming in the Cloud podcasts. Free.
DevOps Weekly has been curating this field since 2010 and SRE Weekly since 2015, which means the patterns your peers treat as obvious were usually explained there first. TLDR Dev reaches nearly half a million engineers daily. Showing up to an incident review having never read about that failure mode is a choice.
Start the DevOps and Site Reliability Engineers bundle →Trusted by the people ahead of you · one briefing · free to start
Questions
- What newsletters should a site reliability engineer read?
- Two curated weeklies and a daily wire cover the field. SRE Weekly collects incident reports and reliability writing, DevOps Weekly covers tooling and practice, TLDR Dev keeps you current daily, and Last Week in AWS tracks cloud changes and their costs. Hark News reads all four to you as a single briefing.
- Which newsletter is best for learning from incidents?
- SRE Weekly, without much competition. Lex Neva has curated it since 2015 specifically around availability, incident response and human factors, so it is the most reliable route to public postmortems and the reasoning behind them.
- Is DevOps Weekly still worth reading after all these years?
- Its age is the argument for it. Running since 2010 means the curation has survived several complete turns of the tooling fashion cycle, which tends to produce better judgment about what will still matter next year than a newer list chasing releases.
- How is this different from a software engineering reading list?
- They share a daily wire, because platform engineers still need general engineering news. The difference is that this bundle adds reliability and cloud economics: incident practice, availability, and what infrastructure changes cost. A general engineering list weights languages, frameworks and career craft instead.
- Do I need to use AWS for Last Week in AWS to be useful?
- It helps, but the cost and architecture reasoning travels. Corey Quinn writes about cloud economics generally, and the pattern of a provider shipping a service that quietly reprices your architecture is not unique to one vendor.
- Are these newsletters free?
- Yes, all four are free to subscribe to. Three are independent curated newsletters and TLDR Dev is free and ad-supported.
- When should I schedule this briefing?
- You choose the time. On-call engineers often set it early so the briefing is done before standup, and because three of these four are weekly, the day a weekly lands is when the briefing runs deepest.