What this site is.

One continuous question.

The topics here are not separate disciplines. They are one continuous question: how does an engineering organization ship work without losing the property that the work was reviewed? Each topic answers a slice of it. The set isn't closed. Others land here when they earn their place.

• DevOps: The production line itself.
• SRE: Running production.
• AI Engineering: AI as a reviewable tool.
• Platforms: The substrate.

Articles and notes.

Two formats. Articles are long-form positions written to be read more than once. Notes are short: sub-arguments, reactions, edge cases that didn't justify their own article.

Articles are the scaffolding. Notes are how the scaffolding adapts.

What gets to be an article.

An article here argues a specific position (DevOps is a production line, not a tooling movement) and holds that position long enough that the argument is worth quoting in a meeting. The bar isn't novelty. It's whether the argument changes how a reader thinks about the next decision.

Most thoughts don't become articles. Most become notes, or get cut entirely.

Editorial standards.

• Positions, not summaries. The articles take a side. Roundups belong elsewhere.
• Lineage, not novelty. Most of what's here has been said before by someone smarter, usually in manufacturing engineering, lean software, or the first SRE book. The site names the lineage when it's there.
• Reference once, read often. Articles are written to be cited, not to perform.
• No bylines. The arguments stand on their reasoning. Author identity is a distraction from whether the argument holds.

How updates work.

Articles get an updatedAt date when they change in substance. Typos don't trigger one. Those are amendments, not revisions. Both show up in the RSS feed and sitemap with their dates.

Source.

The site lives at github.com/bluecloud-dev. Open an issue to flag an error, suggest a topic, or argue with a position. Email lands in the editorial inbox at hello@bluecloud.dev.