I’ve been doing this “reliability” stuff for a little while now (~5 years), at companies ranging from about 20 developers to over 2,000. I’ve always cared primarily about the software elements I describe as living “outside” the application – like, how does it get its configuration? What kinds of instances does it run on, and are those the best kinds to use? What steps does it take on its path from “code in a repository” to “running in production”? And I’ve always kept track of what I liked – which mechanisms allowed fast iteration and which caused frustration, which led to outages and which prevented them.

Changelog offers insights into open-source software development, industry news, and community-driven projects, providing podcasts, articles, and interviews to stay updated with the latest trends and advancements in technology. By exploring Changelog's curated content, developers can learn about new programming languages, frameworks, and tools, as well as contribute to open-source projects and engage with the developer community. Whether you're a software engineer, tech enthusiast, or open-source advocate, Changelog provides resources to keep you informed and inspired in the world of open-source software.

Changelog

The SRE has been doing this ‘reliability’ stuff for a little while now, at companies ranging from about 20 developers to over 2,000. It’s industry standard for a reason – wrangling dependencies in environments with tools like Chef or Ansible loses to these nice self-contained artifacts any day.

How to Build Software like an SRE

Merging (where we’re going, we don’t need tests)

<p>Enjoyed this read, shows how far off we are. But gives us a target.</p>
