{
  "source_file": "0930",
  "source_platform": "Dev.to",
  "author": "Tae Kim",
  "title_listed": "When I killed the Korean version: what channel mismatch actually looks like",
  "keywords": "",
  "domain": "机器学习",
  "content_type": "深度技术解析",
  "is_paid_flag": "否",
  "url": "https://dev.to/hannune/when-i-killed-the-korean-version-what-channel-mismatch-actually-looks-like-ll2",
  "publish_date": "2026-09-15",
  "corpus_stage": "",
  "notes": "",
  "id": "59c1c8bc0fd1",
  "collected_at": "2026-10-02T14:03:46",
  "title": "When I killed the Korean version: what channel mismatch actually looks like - DEV Community",
  "body_markdown": "About three months into building the Korean version, I showed the product to a financial analyst at a Korean institutional investor. He scrolled through the interface for maybe thirty seconds, then said something like: \"we already have Bloomberg for data, what I need is something I can hand off.\"\nThe \"hand off\" part is what stuck. He needed a PDF or an Excel file, something he could email to a manager. The graph query interface I was showing him was not the answer.\nI kept working on the project for a few more weeks anyway. The pipeline was running. I told myself I was still gathering information.\nSome background: 2asy.ai tracks tariff policy changes and how they propagate to specific companies. The basic idea is that you can crawl policy and trade news, figure out which companies sit in the affected supply chains, and make that queryable. The entity resolution work is the hard part of it, which is mostly what the ER API does. When I decided to do a Korean-language version, it looked tractable because I'd done most of that infrastructure already. Mainly crawl pipeline work and some frontend localization to do on top.\nBy the time I showed the analyst that demo, I'd had a few other conversations in the same vein. Different people, similar answer. Korean institutional finance and compliance people I was talking to wanted a deliverable they could hand to someone else, not a tool they'd query themselves. The B2B buyers I'd built the international version for had already decided to integrate vendor risk data programmatically. Most of the Korean buyers I was reaching hadn't made that decision, or weren't the decision-makers who would.\nI paused it. I kept the crawl pipeline and the entity resolution work because those are directly reusable if a reporting-oriented distribution path shows up. But I stopped maintaining it as an active product and turned off the scheduled jobs.\nLooking back, I'm still not entirely sure when I made the decision versus when I just stopped maintaining it. Somewhere around week twelve those converged.\nI build\ner-api\n, a multilingual entity resolution service, and\n2asy.ai\n, a trade intelligence graph. More at\nhannune.ai\n.",
  "metadata": {
    "title": "When I killed the Korean version: what channel mismatch actually looks like - DEV Community",
    "description": "About three months into building the Korean version, I showed the product to a financial analyst at a... Tagged with python, dataengineering, startup, programming.",
    "keywords": "python, dataengineering, startup, programming, software, coding, development, engineering, inclusive, community",
    "author": null,
    "og:type": "article",
    "og:url": "https://dev.to/hannune/when-i-killed-the-korean-version-what-channel-mismatch-actually-looks-like-ll2",
    "og:title": "When I killed the Korean version: what channel mismatch actually looks like",
    "og:description": "About three months into building the Korean version, I showed the product to a financial analyst at a...",
    "og:site_name": "DEV Community",
    "og:image": "https://media2.dev.to/dynamic/image/width=1200,height=627,fit=cover,gravity=auto,format=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fk10l08nooh1uohaklvxp.jpg",
    "twitter:site": "@thepracticaldev",
    "twitter:creator": "@HannuneTech",
    "twitter:title": "When I killed the Korean version: what channel mismatch actually looks like",
    "twitter:description": "About three months into building the Korean version, I showed the product to a financial analyst at a...",
    "twitter:card": "summary_large_image",
    "twitter:widgets:new-embed-design": "on",
    "twitter:image:src": "https://media2.dev.to/dynamic/image/width=1200,height=627,fit=cover,gravity=auto,format=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fk10l08nooh1uohaklvxp.jpg"
  },
  "paywall": {
    "listed_paid": false,
    "detected": false,
    "marker": "",
    "public_only": false,
    "policy": "付费/会员内容只保留页面公开可见部分，不绕过付费墙"
  },
  "crawl": {
    "success": true,
    "status_code": 200,
    "error": ""
  },
  "code_blocks": [],
  "images": [],
  "audio": [],
  "videos": [],
  "links": [
    {
      "href": "https://er-api.hannune.ai/",
      "label": "er-api",
      "type": "a"
    },
    {
      "href": "https://2asy.ai/",
      "label": "2asy.ai",
      "type": "a"
    },
    {
      "href": "https://hannune.ai/",
      "label": "hannune.ai",
      "type": "a"
    }
  ],
  "repair_version": 2,
  "repaired_at": "2026-10-14T10:49:36Z",
  "source_url": "https://dev.to/hannune/when-i-killed-the-korean-version-what-channel-mismatch-actually-looks-like-ll2",
  "papers": [],
  "actual_video_files": [],
  "body_chars": 2175,
  "expected_body_images": 0,
  "discovery_status": "ok",
  "delivery_status": "ok",
  "missing_reason": "",
  "raw_html": "attachments/59c1c8bc0fd1/pages/source.html",
  "local_html": "attachments/59c1c8bc0fd1/pages/article.html",
  "body_base_path": "attachments/59c1c8bc0fd1/pages/",
  "body_markdown_path": "attachments/59c1c8bc0fd1/pages/article.md"
}