<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Ops Development on SRE Engineering Practice</title><link>https://www.sre.wang/en/tags/ops-development/</link><description>Recent content in Ops Development on SRE Engineering Practice</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Thu, 27 Aug 2026 10:36:31 +0800</lastBuildDate><atom:link href="https://www.sre.wang/en/tags/ops-development/index.xml" rel="self" type="application/rss+xml"/><item><title>From "@ Ops in Chat" to Self-Service: 6-Layer Architecture and 4 Landing Phases for Platformizing 20+ Operations</title><link>https://www.sre.wang/en/posts/ops-self-service-platform/</link><pubDate>Thu, 27 Aug 2026 10:36:31 +0800</pubDate><guid>https://www.sre.wang/en/posts/ops-self-service-platform/</guid><description>Operations platformization in practice: move high-frequency manual ops—service restarts, cache clearing, scaling, log retrieval—into a self-service platform. This article breaks down the 6-layer architecture, operation catalog standardization with YAML, double-review engineering for high-risk ops, real pitfalls like approval-bypass and non-idempotent re-runs, plus build-vs-buy guidance against Spug, BlueKing, and Rundeck.</description></item></channel></rss>