Tag: developer-experience
All the articles with the tag "developer-experience".
-
A Week of Firestore / Cloud Functions Footguns — Same GMAT Question Bank
Eight bugs I hit in one week on the same Firebase project (a GMAT question bank): Firestore rules, composite indexes, error_logs spam, TPA scoring, App Check tokens, and a browser-translation DOM crash — symptom, root cause, fix for each.
-
Eight Days of Silent Failure: launchd Fired on Schedule, Nothing Happened
A local pipeline that auto-publishes a video every day at 09:00 failed for eight straight days. launchd fired on schedule, zero alerts. Notes from tracing a path desync down to exit 127.
-
The Day Opus 4.8 Went Haywire: tool call cannot be parsed
A one-day timeline from 2026-06-02: from hopping on X for moral support, to someone finally pinning down the root cause of tool call cannot be parsed.
-
A Week of Making Tutorial Videos With Claude Code: Remotion Animation and ffmpeg Pitfalls
Production pitfalls from a week of making two tutorial videos: subtitle restraint, font size, animation anchor auditing, Remotion render crashes, normalizing quiet narration, and opencc over-localization.
-
一週 Firestore / Cloud Functions 踩坑合輯——同一個 GMAT 題庫系統
一週內在同一個 Firebase 專案（GMAT 題庫系統）連環踩到的 Firestore 權限、composite index、error_logs 洗版、TPA 計分、App Check token、瀏覽器翻譯 DOM crash 八個坑——每坑現象、根因、解法。
-
靜默連敗 8 天：launchd 照常觸發，卻什麼都沒發生
一條每天 09:00 自動發片的本機 pipeline 連敗 8 天，launchd 照常觸發、零告警。記一次從搬檔到 exit 127 的脫鉤排查。
-
Opus 4.8 全線抽風的一天：tool call cannot be parsed
2026-06-02 一整天的事件線：從上 X 抱團取暖，到 tool call cannot be parsed 的根因被人找出來。
-
用 Claude Code 做教學影片一週踩到的坑——Remotion 動畫與 ffmpeg 後製
這一週做兩部教學影片踩到的製作坑：字幕克制、字級、動畫錨點稽核、Remotion render crash 拆段、安靜旁白正規化、opencc 過度在地化。
-
Two HTML/PDF Rendering Traps: Chrome Print Margin and qlmanage's Single-Page Problem
This week I exported a client proposal as HTML→PDF and split an internal report from PDF→images page by page. Both flows had a seemingly unsolvable trap. Each fix is one line of code, but tracking down that line cost me real time.
-
兩個 HTML / PDF 渲染陷阱：Chrome print margin 和 qlmanage 的 1 張縮圖
這禮拜寫了客戶提案的 HTML→PDF 和內部報告的 PDF→圖逐頁拆分，兩個流程都有一個看似無解的陷阱。解法都是一行事情，但找到那一行花了我一小時。
-
Digging into Claude Code's JSONL: Manual Context Usage, Cache Types, and Compact Detection
Claude Code's `/stats` only tells you the total token count, but the JSONL files hide a lot more—cache types, compact triggers, image-triggered cache misses. Here are the useful formulas I collected while building cc-audit.
-
挖 Claude Code 的 JSONL：手動算 context 用量、分辨快取類型、偵測 compact
Claude Code 的 `/stats` 只告訴你總 token 數，但 JSONL 檔案裡其實藏著更細的資訊——快取類型、compact 觸發、貼圖 cache miss 都能手動算。這是我最近做 cc-audit skill 時整理出來的幾個實用公式。
-
Why Does Cowork Hit Your Limit in Hours While Claude Code Runs All Day?
Same Max plan, same Claude — but Cowork burns through tokens ten times faster. Here's why, and when to use which.
-
為什麼 Cowork 幾小時就頂到限額，Claude Code 整天都沒事？
同樣是 Max 方案，Cowork 和 Claude Code CLI 的 token 消耗差距可以到十倍以上。這篇解釋為什麼，以及什麼時候用哪個。
-
The 5 Levels of Claude Code: You Don't Choose to Upgrade, the Ceiling Forces You
From Raw Prompting to Orchestration — the 778-upvote Reddit framework where every level exists because the previous one broke.
-
Claude Code 五個成熟度等級：你不是選擇升級的，是被天花板逼的
從 Raw Prompting 到 Orchestration，Reddit 上 778 個讚的框架——每一層存在的原因，是因為上一層壞掉了。
-
The Real Next Level in Claude Code: Context Management and Hooks
From Claude.md to Hooks — sharing the context management upgrade after heavy daily Claude Code usage. When rules pile up and compliance drops, Hooks become the perfect gatekeeper.
-
Claude Code 的真正進階：上下文管理與 Hooks
從 Claude.md 到 Hooks，分享大量使用 Claude Code 後對上下文管理的理解升級。規則塞太多怎麼辦？Hooks 就是那個完美的守門員。
-
Claude Code Initial Prompt Tips: Six Techniques for Effective AI Collaboration
Six practical tips for writing effective initial prompts in Claude Code, from clarifying your goals to leveraging plan mode for better AI collaboration.
-
Claude Code 起始指令心法：六個讓 AI 真正聽懂你的技巧
分享六個下 Claude Code 起始指令的實戰心法，從釐清目標到善用計畫模式，讓你的 AI 協作更高效。
-
What I Learned from 7,843 Claude Code Conversations
46 days, 6 projects, 7,843 conversations. This is not a manual — it's a diary of trial and error.
-
Claude Code 用了 7843 條對話後的心得
46 天、6 個專案、7843 條對話，整理出來的 Claude Code 實戰心法。不是教學手冊，是踩坑日記。
-
Building AI Products from Scratch: A Non-Engineer's Four-Generation Evolution
A teacher-turned-builder shares the real story of four generations of AI tool development—RAG, platform architecture, cross-border deployment, and open-source strategy, with all the pitfalls along the way.
-
從零打造 AI 產品的踩坑日記：一個非工程師的四代進化
一個教學從業者，從 GPT 自訂 Agent 起步，歷經四代 AI 工具開發，分享 RAG、平台架構、跨國部署、開源策略的真實踩坑紀錄。
-
The Dunning-Kruger Curve of Claude Code: From Clueless to Perfect Sync
A heavy user with zero engineering background shares the Dunning-Kruger curve of Claude Code from day one to week three, and the workflow that finally clicked.
-
Claude Code 的達克曲線：從陌生到極致同步的實戰心得
一個非工程師背景的重度使用者，分享 Claude Code 從第一天到第三週的達克曲線效應，以及最終找到的高效互動方式。