
  <rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
    <channel>
      <title>Chaos and Order</title>
      <link>https://www.youngju.dev/blog</link>
      <description>천천히 올바르게. AI Researcher &amp; DevOps Engineer Youngju&#39;s blog. GPU/CUDA, LLM, MLOps, Kubernetes AI workloads, and data engineering — plus mindset essays on confidence, routines, health, and sport psychology.</description>
      <language>ko</language>
      <managingEditor>fjvbn2003@gmail.com (Youngju Kim)</managingEditor>
      <webMaster>fjvbn2003@gmail.com (Youngju Kim)</webMaster>
      <lastBuildDate>Sat, 15 Aug 2026 00:00:00 GMT</lastBuildDate>
      <atom:link href="https://www.youngju.dev/tags/개발문화/feed.xml" rel="self" type="application/rss+xml"/>
      
  <item>
    <guid>https://www.youngju.dev/blog/architecture/2026-08-15-guide-code-review.en</guid>
    <title>The Complete Guide to Code Review: Designing Review as a Process</title>
    <link>https://www.youngju.dev/blog/architecture/2026-08-15-guide-code-review.en</link>
    <description>Treats code review not as a conversation but as a system with throughput, latency and ownership. Covers documenting the approval standard, change size, the one-business-day response rule, splitting work between humans and automation, ownership and approval rules, comment severity levels, escalation when agreement fails, and the ways review metrics get misused.</description>
    <pubDate>Sat, 15 Aug 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>코드리뷰</category><category>개발문화</category><category>code-review</category><category>process</category><category>automation</category><category>metrics</category>
  </item>

  <item>
    <guid>https://www.youngju.dev/blog/architecture/2026-08-15-guide-code-review.ja</guid>
    <title>コードレビュー 完全ガイド: レビューをプロセスとして設計する</title>
    <link>https://www.youngju.dev/blog/architecture/2026-08-15-guide-code-review.ja</link>
    <description>コードレビューを会話ではなく、スループット・レイテンシ・所有権を持つシステムとして扱います。承認基準の文書化、変更サイズ、1営業日の応答規則、人と自動化の分担、所有権と承認規則、コメントの等級、合意できないときのエスカレーション、そしてレビュー指標が誤用される仕方までを運用の観点で整理します。</description>
    <pubDate>Sat, 15 Aug 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>코드리뷰</category><category>개발문화</category><category>code-review</category><category>process</category><category>automation</category><category>metrics</category>
  </item>

  <item>
    <guid>https://www.youngju.dev/blog/architecture/2026-08-15-guide-code-review</guid>
    <title>코드 리뷰 완전 가이드: 리뷰를 프로세스로 설계하기</title>
    <link>https://www.youngju.dev/blog/architecture/2026-08-15-guide-code-review</link>
    <description>코드 리뷰를 대화가 아니라 처리량·지연 시간·소유권을 가진 시스템으로 봅니다. 승인 기준의 문서화, 변경 크기, 1영업일 응답 규칙, 사람과 자동화의 분담, 소유권과 승인 규칙, 코멘트 등급, 교착 시 에스컬레이션, 그리고 리뷰 지표가 오용되는 방식까지 운영 관점에서 정리합니다.</description>
    <pubDate>Sat, 15 Aug 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>코드리뷰</category><category>개발문화</category><category>code-review</category><category>process</category><category>automation</category><category>metrics</category>
  </item>

    </channel>
  </rss>
