
  <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>Tue, 21 Jul 2026 00:00:00 GMT</lastBuildDate>
      <atom:link href="https://www.youngju.dev/tags/web-novel/feed.xml" rel="self" type="application/rss+xml"/>
      
  <item>
    <guid>https://www.youngju.dev/blog/storytelling/web-novel-grammar.en</guid>
    <title>Why Regression, Possession, and Reincarnation Work So Well — Dissecting the Grammar of Web Novels</title>
    <link>https://www.youngju.dev/blog/storytelling/web-novel-grammar.en</link>
    <description>Before you write web novels off as juvenile, look at why the form is shaped the way it is and the story changes. The information asymmetry manufactured by regression, possession, and reincarnation; the emotional rhythm Korean readers call cider and sweet potato; the status window that turns a game UI into narration — all of it is precise engineering produced by a distribution model of daily serialization and pay-per-episode. With representative works alongside, this piece dissects the grammar of the web novel and asks what the form invented that the traditional novel never had.</description>
    <pubDate>Tue, 21 Jul 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>storytelling</category><category>web-novel</category><category>fiction</category><category>narrative</category><category>culture</category>
  </item>

  <item>
    <guid>https://www.youngju.dev/blog/storytelling/web-novel-grammar.ja</guid>
    <title>回帰・憑依・転生はなぜこれほど効くのか — ウェブ小説の文法を解剖する</title>
    <link>https://www.youngju.dev/blog/storytelling/web-novel-grammar.ja</link>
    <description>ウェブ小説を幼稚だと片づけてしまう前に、その形式がなぜそういう形をしているのかを見ると、話が変わってきます。「回帰・憑依・転生」がつくり出す情報の非対称、「サイダーとサツマイモ」と呼ばれる感情のリズム、ステータス画面というゲームUIの物語化 — これらはすべて、毎日連載され一話ごとに課金されるという流通構造が生み出した精巧な設計です。代表作とともにウェブ小説の文法を解剖し、この形式が従来の小説になかった何を発明したのかを考えます。</description>
    <pubDate>Tue, 21 Jul 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>storytelling</category><category>web-novel</category><category>fiction</category><category>narrative</category><category>culture</category>
  </item>

  <item>
    <guid>https://www.youngju.dev/blog/storytelling/web-novel-grammar</guid>
    <title>회귀·빙의·환생은 왜 이렇게 잘 먹히나 — 웹소설의 문법 해부</title>
    <link>https://www.youngju.dev/blog/storytelling/web-novel-grammar</link>
    <description>웹소설을 유치하다고 넘기기 전에, 그 형식이 왜 그렇게 생겼는지 보면 이야기가 달라집니다. 회빙환(회귀·빙의·환생)이 만드는 정보 비대칭, 사이다와 고구마라는 감정 리듬, 스테이터스 창이라는 게임 UI의 서사화 — 이 모든 것은 매일 연재되고 편당 결제되는 유통 구조가 만들어 낸 정교한 설계입니다. 대표작과 함께 웹소설의 문법을 해부하고, 이 형식이 전통 소설에 없는 무엇을 발명했는지 이야기합니다.</description>
    <pubDate>Tue, 21 Jul 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>storytelling</category><category>web-novel</category><category>fiction</category><category>narrative</category><category>culture</category>
  </item>

  <item>
    <guid>https://www.youngju.dev/blog/storytelling/web-novel-grammar.zh</guid>
    <title>回归·穿书·重生为何屡试不爽 — 解剖网络小说的语法</title>
    <link>https://www.youngju.dev/blog/storytelling/web-novel-grammar.zh</link>
    <description>在把网络小说当作幼稚读物略过之前，不妨看看它的形式为什么长成这样，故事就会不一样。“回归·穿书·重生”制造的信息不对称，被称作“汽水与红薯”的情绪节奏，把游戏 UI 搬进叙事的状态栏 — 这一切都是每日连载、按话付费的流通结构催生出的精密设计。本文结合代表作解剖网络小说的语法，并追问这种形式发明了传统小说所没有的什么东西。</description>
    <pubDate>Tue, 21 Jul 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>storytelling</category><category>web-novel</category><category>fiction</category><category>narrative</category><category>culture</category>
  </item>

    </channel>
  </rss>
