[{"data":1,"prerenderedAt":251},["ShallowReactive",2],{"\u002Fblog\u002Ftui-cognitive-bandwidth\u002F:zh-Hant":3,"\u002Fblog\u002Ftui-cognitive-bandwidth\u002F-surround:zh-Hant":145,"blog-all-posts:zh-Hant":146},{"id":4,"title":5,"author":6,"body":10,"date":127,"description":128,"extension":129,"image":130,"locale":131,"meta":132,"minRead":133,"navigation":134,"original":135,"path":136,"pinned":135,"seo":137,"source":138,"sourceUrl":23,"stem":139,"tags":140,"updated":130,"__hash__":144},"blog\u002Fblog\u002Ftui-cognitive-bandwidth.zh-Hant.md","TUI 正在殺死你的認知頻寬：AI Coding 的「極客濾鏡」該碎了",{"name":7,"avatar":8},"陳大黃",{"src":9,"alt":7},"\u002Favatar.jpg",{"type":11,"value":12,"toc":118},"minimark",[13,28,31,34,37,42,45,48,51,54,57,60,63,71,74,77,83,86,89,93,96,99,102,106,109,112,115],[14,15,16],"blockquote",{},[17,18,19,20,27],"p",{},"核心觀點首發於 ",[21,22,26],"a",{"href":23,"rel":24},"https:\u002F\u002Fx.com\u002Frealchendahuang\u002Fstatus\u002F2087949416808518106",[25],"nofollow","X","，這篇文章是完整版論述。",[17,29,30],{},"現在一堆 AI Coding Agent 動不動就上 TUI，這股風氣，Claude Code 得負很大責任。它把「在終端裡跟 AI 對話寫代碼」這件事做得很極致，但也把一條審美和路徑依賴帶了起來：好像真正高級的 Coding Agent，就得默認是終端介面；Web 端反而是附屬，甚至被嘲成「不夠程式設計師」。",[17,32,33],{},"結果呢？先搞一個複雜的 TUI，各種顏色、狀態列、快捷鍵、模式切換，然後美其名曰「沉浸式」「高效」「尊重程式設計師」。",[17,35,36],{},"真的嗎？",[38,39,41],"h2",{"id":40},"你以為在對話其實在搏鬥","你以為在對話，其實在搏鬥",[17,43,44],{},"對一小部分每天泡在終端的人來說，TUI 確實爽。但對更多人來說，它是在人為製造門檻。用 TUI 跟 Agent 協作時，你其實在不斷做三件事：",[17,46,47],{},"**回憶快捷鍵和模式。**每個工具都有一套自己的鍵位習慣，新用戶一臉懵，老用戶換工具也得重新適應。",[17,49,50],{},"**在滾動的字符流裡定位信息。**狀態不是攤開給你看的，而是埋在時間軸裡的，你得靠滾動和搜索去「考古」。",[17,52,53],{},"**祈禱自己沒有誤觸進入某個奇怪狀態。**模式切換是隱形的，你經常不知道自己當前處於哪個模式，直到出了問題。",[17,55,56],{},"這已經不是互動了，這是在跟介面搏鬥。",[38,58,59],{"id":59},"信息密度不等於信息效率",[17,61,62],{},"TUI 的辯護者最愛說的一個詞是「信息密度」。但信息密度堆到極致，代價是可讀性和可恢復性被踩到最低。",[17,64,65,66,70],{},"真正高效的介面，應該是",[67,68,69],"strong",{},"把狀態攤開給你看","，讓你用眼睛和空間感去理解——哪個任務在跑、哪條會話在等輸入、哪個文件被改了，一眼掃過去就知道。而不是逼你把所有東西都塞進短期記憶裡，用腦子維護一張「當前系統狀態」的隱形地圖。",[17,72,73],{},"人的工作記憶只有四到七個槽位。TUI 的互動模型，本質上是把最寶貴的認知資源花在「記住介面狀態」上，而不是「思考問題」上。",[38,75,76],{"id":76},"它還在培養一種壞習慣",[17,78,79,80],{},"更糟的是，TUI 生態在培養一種很壞的價值判斷：",[67,81,82],{},"把會不會用某個工具的鍵位當成能力本身。",[17,84,85],{},"結果就是，人花大量精力在適應介面，而不是在思考問題。衡量一個程式設計師的標準，變成了「能不能背誦這套快捷鍵」，而不是「能不能把問題拆解清楚」。",[17,87,88],{},"一個好的工具應該降低思考成本，而不是把思考成本轉移到「如何操作這個介面」上。",[38,90,92],{"id":91},"web-ui-完全可以又快又乾淨","Web UI 完全可以又快又乾淨",[17,94,95],{},"有人說 Web 端慢、不夠「原生」。2026 年了，這個論點早就站不住了。",[17,97,98],{},"Web UI 完全可以做得又快又乾淨：裝成 PWA 之後跟桌面客戶端幾乎沒有區別，更新還更方便——不用用戶手動升級，刷新一下就是最新版。長會話、多任務並行、任務狀態可視化，這些恰恰是瀏覽器 DOM 的強項，而不是字符流的強項。",[17,100,101],{},"我自己的主力配置就是 OpenChamber 這種 Web 介面 + OpenCode 內核，長期高強度使用，穩得很。真要認真挑刺的話，Web 端偶爾的小毛病遠不影響長期使用，倒是某些 TUI 的模式切換坑過我很多次。",[38,103,105],{"id":104},"工具是給人用的不是用來證明誰更極客的","工具是給人用的，不是用來證明誰更「極客」的",[17,107,108],{},"Claude Code 本身很強，這點沒問題。但它把「TUI 才是正統」這個審美和路徑依賴帶起來了，後面一堆跟風的就更離譜——連互動設計都懶得做，直接把「長在終端裡」當成高級的證明。",[17,110,111],{},"把反人類的互動包裝成高級，真是很滑稽的一件事情。",[17,113,114],{},"工具是給人用的。判斷標準應該永遠是：**它有沒有降低你完成任務的總成本？**如果一套介面讓你把精力花在「跟介面搏鬥」上，那它再「極客」也是負資產。",[17,116,117],{},"下次選 Coding Agent 的時候，把這個濾鏡摘了再選。",{"title":119,"searchDepth":120,"depth":120,"links":121},"",2,[122,123,124,125,126],{"id":40,"depth":120,"text":41},{"id":59,"depth":120,"text":59},{"id":76,"depth":120,"text":76},{"id":91,"depth":120,"text":92},{"id":104,"depth":120,"text":105},"2026-09-09","一堆 AI Coding Agent 搶著上 TUI，把互動塞回 80 年代的終端範式，還美其名曰「沉浸式」「尊重程式設計師」。這篇文章拆解 TUI 系統性降低認知頻寬的三個機制，以及 Web UI 為什麼才是正解。","md",null,"zh-Hant",{},7,true,false,"\u002Fblog\u002Ftui-cognitive-bandwidth",{"title":5,"description":128},"x","blog\u002Ftui-cognitive-bandwidth.zh-Hant",[141,142,143],"AI 程式設計","互動設計","隨筆","ToFR_6LwRUhZPNXPn2jBQ-NUWg39obd9D10ySn3CUjM",[130,130],[147,156,165,174,180,188,195,202,210,216,223,232,234,242],{"path":148,"title":149,"description":150,"date":151,"minRead":152,"tags":153},"\u002Fblog\u002Fagent-harness-selection","試遍了 Pi Agent、OMP、Codex、ZCode，我最後為什麼選了 OpenCode + OpenChamber","試過一輪 Agent Harness 後的選型復盤：以 GUI 體驗、供應商綁定、二次開發自由度三個標準，排除了 Pi Agent、OMP、Codex、ZCode，最後選了 OpenCode 核心 + OpenChamber 介面。","2026-08-06",6,[154,155],"AI Agent","工具選型",{"path":157,"title":158,"description":159,"date":160,"minRead":152,"tags":161},"\u002Fblog\u002Fcloudflare-broke-stack","2026 獨立開發最佳實踐：Cloudflare 窮鬼全家餐","獨立開發者的零成本技術棧：Codex 寫程式、GitHub 管版本、Stripe 收款，前端 TanStack Start、後端 Hono + Workers、資料庫 D1、儲存 R2、快取 KV，全部跑在 Cloudflare 上。","2026-06-15",[162,163,164],"Cloudflare","獨立開發","技術棧",{"path":166,"title":167,"description":168,"date":169,"minRead":152,"tags":170},"\u002Fblog\u002Fdeepseek-api-web-search","DeepSeek API 內建聯網搜尋，Responses API 白拿官方搜尋能力","DeepSeek 官方在 API 裡內建了聯網搜尋：用 Responses 介面呼叫 deepseek-v4-flash，宣告 web_search 工具即可，不用自己接第三方搜尋引擎，也不用申請搜尋金鑰。","2026-08-05",[171,172,173],"DeepSeek","API","AI 工具",{"path":175,"title":176,"description":177,"date":169,"minRead":133,"tags":178},"\u002Fblog\u002Fdeepseek-v4-flash-review","DeepSeek V4 Flash 正式版深度體驗：便宜、快、1M 上下文、內建搜尋","深度體驗了幾天 DeepSeek V4 Flash 正式版：極致的便宜、快如閃電、1M 上下文、官方內建聯網搜尋、完全開源。唯一的短板是多模態，但可以組合其他模型補上。",[171,179,173],"模型評測",{"path":181,"title":182,"description":183,"date":160,"minRead":184,"tags":185},"\u002Fblog\u002Ffree-cloudflare","免費使用者如何榨乾 Cloudflare，免費版到底能白嫖到什麼程度？","Cloudflare 免費版能撐起一整套個人網路基礎設施：DNS、CDN、Pages、Workers、KV、D1、R2、信箱、Tunnel、AI 閘道等。",8,[162,186,187],"免費額度","部署",{"path":189,"title":190,"description":191,"date":127,"minRead":184,"tags":192},"\u002Fblog\u002Fmodel-harness-decoupling","原廠 Harness 未必是版本答案：開放模型時代，模型和 Harness 要分開選","用 Claude 就上 Claude Code？開放模型時代這個直覺該升級了。原廠的優勢是真的，但訓練好模型和做好 Harness 是兩門工程——這篇文章講清楚為什麼模型與 Harness 已經可以分開選，以及五家 Harness 的定位地圖。",[154,193,194],"Harness","選型",{"path":196,"title":197,"description":198,"date":127,"minRead":184,"tags":199},"\u002Fblog\u002Fopencode-productive-stack","穩定、快速、高產、便宜：我的 AI Coding 全家桶實錄","OpenCode + OpenChamber + 兩份 DeepSeek V4 Flash 訂閱，15 個項目同時跑代碼，額度只掉一點點。這篇文章攤開我的完整配置：上下文剪枝、分層記憶、桌面自動化，以及「原湯化原食」的選型教訓。",[200,141,201],"OpenCode","配置",{"path":203,"title":204,"description":205,"date":206,"minRead":207,"tags":208},"\u002Fblog\u002Fproduct-faxin-principle","發心原理：獨立開發者為什麼要學會捨棄","你為什麼出發？你為誰出發？你到底想解決哪一個問題？產品的鋒利感來自捨得和放棄。","2026-06-20",10,[209,163],"產品思維",{"path":211,"title":212,"description":213,"date":206,"minRead":184,"tags":214},"\u002Fblog\u002Fproduct-pain-vs-itch","使用者說「很屌」別上頭：痛點與癢點","口頭喜歡一文不值。判斷需求只有一個硬標準：看使用者願意付出什麼。",[209,215],"需求判斷",{"path":217,"title":218,"description":219,"date":151,"minRead":220,"tags":221},"\u002Fblog\u002Fqwen-vision-for-deepseek","給 DeepSeek 補上多模態：Qwen-3.7-Flash 識圖方案","DeepSeek V4 Flash 沒有多模態，識圖怎麼辦？研究後目前 CP 值最高的方案是 Qwen-3.7-Flash：辨識一張圖片成本極低，和 V4 Flash 組合使用補齊短板。",5,[171,222,179],"多模態",{"path":224,"title":225,"description":226,"date":227,"minRead":228,"tags":229},"\u002Fblog\u002Fsub-store-cloudflare","我把機場訂閱聚合搬到了 Cloudflare 上","多個機場加自建節點合成一條訂閱，分流規則在伺服器端配好，用戶端只管訂閱。","2026-06-28",4,[162,230,231],"翻牆","開源專案",{"path":136,"title":5,"description":128,"date":127,"minRead":133,"tags":233},[141,142,143],{"path":235,"title":236,"description":237,"date":238,"minRead":152,"tags":239},"\u002Fblog\u002Fvalue-not-external","討論有沒有價值，這件事本身就沒有價值","我們的價值不由任何人定義。人在 AI 時代，到底應該如何理解自己。","2026-06-18",[240,241],"AI 思考","人文隨筆",{"path":243,"title":244,"description":245,"date":246,"minRead":247,"tags":248},"\u002Fblog\u002Fx-growth-1000-followers","一天多漲粉 1000+，我做了什麼","6 月認真經營 X，一天多漲粉 1000+。這篇記錄我當時做過的事和得到的回饋。","2026-06-16",12,[249,250],"X 經營","內容增長",1789752318093]