洪 民憙 (Hong Minhee)

Hello! I'm Hong Minhee (洪 民憙), an open source software engineer in my late 30s, living in Seoul, Korea. I'm bisexual and non-binary (they/them), and an enthusiastic advocate of free/open source software and the fediverse.

I work full-time on @fedify, an ActivityPub server framework in TypeScript, funded by @sovtechfund. I'm also the creator of @hollo, a single-user ActivityPub microblog; @botkit, an ActivityPub bot framework; Hackers' Pub, a fediverse platform for software developers; and LogTape, a logging library for JavaScript and TypeScript.

I have a long interest in East Asian languages (CJK) and Unicode. I post mostly in English here, though occasionally in Japanese or in mixed-script Korean (國漢文混用體), a traditional writing style that interleaves Chinese characters with the native Korean alphabet. Wanting to write in that style was actually one of the reasons I joined the fediverse. Feel free to talk to me in English, Korean, Japanese, or even Literary Chinese!

#introduction

はじめまして！ソウル在住の30代後半のオープンソースソフトウェアエンジニア、洪 民憙（ホン・ミンヒ）と申します。バイセクシュアル（bisexual）・ノンバイナリー（non-binary）で、自由・オープンソースソフトウェア（F/OSS）とフェディバース（fediverse）の熱烈な支持者です。

STF（@sovtechfund）の支援を受け、TypeScript用ActivityPubサーバーフレームワーク「@fedify」の開発に専念しています。他にも、おひとり様向けのActivityPubマイクロブログ「@hollo」、ActivityPubボットフレームワーク「@botkit」、ソフトウェア開発者向けフェディバースプラットフォームHackers' Pub、JavaScript・TypeScript用ロギングライブラリLogTapeなどの制作者でもあります。

東アジア言語（いわゆるCJK）とUnicodeにも興味があります。このアカウントでは主に英語で投稿していますが、時々日本語や国漢文混用体（漢字ハングル混じり文）の韓国語でも書いています。実はこの文体で書きたくてフェディバースを始めた、という経緯もあります。日本語、英語、韓国語、漢文でも気軽に話しかけてください！

#自己紹介

安寧(안녕)하세요! 저는 서울에 살고 있는 30代(대) 後半(후반)의 오픈 소스 소프트웨어 엔지니어 洪民憙(홍민희)입니다. 兩性愛者(양성애자)(bisexual)이자 논바이너리(non-binary)이며, 自由(자유)·오픈 소스 소프트웨어(F/OSS)와 聯合宇宙(연합우주)(fediverse)의 熱烈(열렬)한 支持者(지지자)이기도 합니다.

STF(@sovtechfund)의 支援(지원)을 받아 TypeScript用(용) ActivityPub 서버 프레임워크 @fedify 開發(개발)에 專業(전업)으로 任(임)하고 있습니다. 그 外(외)에도 싱글 유저用(용) ActivityPub 마이크로블로그 @hollo, ActivityPub 봇 프레임워크 @botkit, 소프트웨어 開發者(개발자)를 위한 聯合宇宙(연합우주) 플랫폼 Hackers' Pub, JavaScript·TypeScript用(용) 로깅 라이브러리 LogTape 等(등)의 製作者(제작자)이기도 합니다.

東(동)아시아 言語(언어)(이른바 CJK)와 Unicode에도 關心(관심)이 많습니다. 이 計定(계정)에서는 主(주)로 英語(영어)로 포스팅하지만, 때때로 日本語(일본어)나 國漢文混用體(국한문 혼용체) 韓國語(한국어)로도 씁니다. 聯合宇宙(연합우주)에 오게 된 動機(동기) 中(중) 하나가 바로 國漢文混用體(국한문 혼용체)로 글을 쓰고 싶었기 때문이기도 하고요. 韓國語(한국어), 英語(영어), 日本語(일본어), 아니면 漢文(한문)으로도 말을 걸어주세요!

#툿친소 #연친소 #별친소 #자기소개

@evan Haha, well if that's the case, how about upgrading to the latest version of Node.js? The latest Node.js version can run TypeScript files natively!

@sublimer はい、それにNode.js単体では型チェックも行われませんよね。ただ、簡単なスクリプトを書く際にはかなり便利だと思います。（型チェックはVisual Studio Codeのようなエディタで行われると想定した場合）

Node.jsでTypeScript使えるやつはあくまでも型情報を落としているだけなので、Node.jsでTypeScriptを直接実行できるけどV8が直接実行しているわけではない
V8が直接TypeScript実行できるようになったらブラウザでもTypeScript使えるようになるのかな

FYI, the latest Node.js can run TypeScript code directly without a build process using the node script.ts command.

@evan I'm not sure if you'll like it, but why don't you give Deno a try? You can run .ts files directly without a separate build pipeline.

@mariusor Deno might be it, but it's run by a VC-funded startup… 😂

@SRAZKVT Yeah, its governance is indeed problematic. I hope they migrate their governance on TypeScript to an independent foundation.

@Razemix Yeah, for simple projects, transpilation would be overkill indeed. By the way, that's why I'd preferred Deno over Node.js. Node.js also transforms TypeScript code by default though.

@gosha Haha, I've always had my doubts about Rails' aesthetics.

@abnv Yeah, that's fair enough indeed!

Is anyone still sticking to #JavaScript instead of using #TypeScript? If so, why are you sticking with it? Please let me know your reasons!

TSKaigi 2026に採択されました。「TypeScriptのclassはなぜこうなったのか」というタイトルで、classの歴史的経緯・落とし穴・使いどころを体系的に整理する30分セッションです。

https://kosui.me/posts/2026/03/tskaigi

📢TSKaigi 2026の基調講演は、MicrosoftのPrincipal Software Engineer、Jake Bailey氏をお迎えします。

TypeScriptチームでパフォーマンスやインフラ、エコシステム整備を主に担当されています。 タイトルは『TS7: How We Got There』。「中の人」のご登壇をお楽しみに！

https://x.com/tskaigi/status/2035661614847001050?s=20

残念ながら落ちてしまった。😭

まあ、それでも参加はするけどね。

https://tskaigi.hatenablog.com/entry/2026/03/22/185722

TSKaigi 2026 プロポーザル採択者発表 https://tskaigi.hatenablog.com/entry/2026/03/22/185722

ついに発表された

We make our choices, and then our choices make us.

https://writings.hongminhee.org/2026/01/ethics-of-small-actions/

TSKaigi 2026の登壇者募集、数日前に締め切られたんだな。私が出したプロポーザルは通るかな？

Quick vibe check on @elk usage.

👉 Have you been using #Elk web app (https://elk.zone)?

Please #boost for science :) We have been discussing the future of Elk and your input here matters a lot. 🙏

Feel free to elaborate on the comments as well!

#askmastodon #askfedi #askmasto #fediverse #mastodon #mastodev

This Marxist lens on the different ways my peers and network are reacting to GenAI was more interesting than I expected

https://writings.hongminhee.org/2026/03/craft-alienation-llm/

LLMコーディングアシスタントはソフトウェアエンジニアたちの亀裂を作ったのではない。すでにあった亀裂を露わにしただけだ。

匠人気質のソフトウェアエンジニアたちが感じる疎外の源泉はLLMではなく、産出物を遅く出す側に不利益を与える市場にある。Marxの労働疎外論でこの問題を読む新しいエッセイを書いた。

「コーディングを愛する人たちが、なぜコーディングから追い出されているのか」

LLM 코딩 어시스턴트는 소프트웨어 엔지니어들 사이의 分裂(분열)을 만든 게 아니다. 이미 있던 分裂(분열)을 드러낸 것이다.

匠人(장인) 氣質(기질)의 소프트웨어 엔지니어들이 느끼는 疎外(소외)의 源泉(원천)은 LLM이 아니다. 그들의 產出物(산출물)을 더 느리게 만드는 쪽에 不利益(불이익)을 주는 市場(시장)이다. Marx의 勞動(노동) 疎外論(소외론)으로 이 問題(문제)를 읽어보는 새 글을 썼다.

〈왜 코딩을 사랑하는 사람들이 코딩에서 밀려나는가〉 (한글)

@evan Totally agree, and I think that's actually the point the essay is trying to make. The split isn't “LLM users vs. craft lovers” but something more like “people with room to choose how they use the tools vs. people who don't have that room.”

@mitchellh is a good example. He's clearly using LLMs as a craftsperson. So am I, I think. But both of us are in situations where we're not being measured against a colleague's output every quarter. The workplace dynamic is what compresses all of that curiosity and exploration into pure throughput.

The craft probably does survive, just not evenly distributed.

As luck would have it, the timing didn't work your way. A re-post hit the front page: https://news.ycombinator.com/item?id=47473178

This is a damn good article, and really makes me think about where I fall on the spectrum.

I didn't have to think very hard, I side firmly with Lawson.

I firmly believe that code is a craft, and I take pride in the time spent writing the code, not just in the product itself.

I mourn the impending loss of that kind of counter-culture approach to programming. Which is ironic because I don't think it's even the mainstream way of looking at coding... most devs I know would side with Orchard. Coding is a means to an end.

Work of the day! Me and my colleague have been making something with fabric and electronics :>

< F/OSS Histomat: We Should Reclaim LLMs, Not Reject Them
>

https://writings.hongminhee.org/2026/01/histomat-foss-llm/

The author argues against withdrawing from AI — instead proposing a Training Copyleft license (a GPLv4 / TGPL), following the same pattern as GPLv2 → GPLv3 → AGPL, each evolving to close new exploitation loopholes.

A NEW VERSION of
Requirements for Hangul Text Layout and Typography
한국어 텍스트 레이아웃 및 타이포그래피를 위한 요구사항
has been published.

https://www.w3.org/TR/klreq/

The content was rearranged to match the standard headings used for the W3C Language Enablement Framework.The document is still in English and Korean, with buttons to switch between.

Going forward, we will now begin adding new content.

I've just submitted my post to Lobsters and Hacker News:

• Lobsters: https://lobste.rs/s/vxsjiv/why_craft_lovers_are_losing_their_craft
• Hacker News: https://news.ycombinator.com/item?id=47468389

LLM coding assistants didn't create a split between craft-lovers and make-it-go developers. They revealed one that was always there.

For craft-lovers, what's being bypassed isn't the output but the act itself. Marx called this separation from the act of production. But the alienation isn't coming from the LLM. It's coming from a market that penalizes whoever produces output more slowly.

Why craft-lovers are losing their craft