<?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>플랫폼 엔지니어링 on After the Code</title><link>https://windshock.github.io/ko/tags/%ED%94%8C%EB%9E%AB%ED%8F%BC-%EC%97%94%EC%A7%80%EB%8B%88%EC%96%B4%EB%A7%81/</link><description>Recent content in 플랫폼 엔지니어링 on After the Code</description><generator>Hugo -- 0.145.0</generator><language>ko-KR</language><lastBuildDate>Tue, 21 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://windshock.github.io/ko/tags/%ED%94%8C%EB%9E%AB%ED%8F%BC-%EC%97%94%EC%A7%80%EB%8B%88%EC%96%B4%EB%A7%81/index.xml" rel="self" type="application/rss+xml"/><item><title>보안 지식 전달에서 기본값 설계로</title><link>https://windshock.github.io/ko/post/2026-04-21-security-knowledge-to-default-design/</link><pubDate>Tue, 21 Apr 2026 00:00:00 +0000</pubDate><guid>https://windshock.github.io/ko/post/2026-04-21-security-knowledge-to-default-design/</guid><description>보안–DevOps 문제를 지식 전달 실패가 아니라 기본값 설계, 인터페이스, 예외 처리, 정렬의 구조 문제로 다시 보는 조직 설계 보고서.</description></item></channel></rss>