Pull to refresh
 2026 iThome Ironman
Series 31 chapters

2026 iThome Ironman

The story begins with a major policy shift at the Ministry of Health and Welfare’s Department of Information Management. After Director-General Chien-Chang Lee took office, the department began promoting FHIR and SMART on FHIR to address the siloed nature of hospital information systems, and even invited one of the founders of SMART to Taiwan. FHIR’s support for multiple programming languages and its Docker-friendly ecosystem aligned perfectly with the author’s preferred technology stack. When the inaugural Taiwan Top 50 SMART Apps program—dubbed the healthcare sector’s equivalent of Taiwan’s 0050 ETF—was launched, the author submitted an application as an opportunity to put the idea to the test. At the outset, this series defines its scope as “SMART on FHIR application development in the broader sense.” It covers not only the core SMART App Launch standard, but also the complete end-to-end development journey of building real-world healthcare applications.

Start reading

Latest Posts

View all posts
4 posts Browse all tags
 2026 iThome Ironman
Series

2026 iThome Ironman

1 chapter 146
Watch Notes
Series

Watch Notes

1 chapter 102

I Work at a Military Hospital, and I Just Claimed Three of AI's Hardest Problems

111 0
SMART on FHIR 火線超人(FHIRLineBot)
Series

SMART on FHIR 火線超人(FHIRLineBot)

1 chapter 145

Latest Wiki

View all wiki
Herdr: What Multiple Machines and Multiple Agents Actually Look Like on Screen, and the Five Places I Could Put It

Herdr: What Multiple Machines and Multiple Agents Actually Look Like on Screen, and the Five Places I Could Put It

In Lex Fridman #501 DHH says he replaced tmux with Herdr. The reason was not that it looks nicer. It was that he had started running agents on four or five machines, and tmux has no idea what is happening inside each pane. This page covers Herdr properly. It works out whether each pane is running, blocked waiting on you, done, or idle, and it marks that state in the sidebar. The part people get wrong is how multiple machines are displayed, so that gets its own section. The answer is that every machine runs its own server, there is no single combined view of all three, and going across machines is an SSH thin client that connects to one machine at a time. DHH's setup uses GL.iNet Comet KVMs plus Tailscale to turn machines scattered across Malibu and Copenhagen into one local network, four to five machines, about three agents each, roughly sixteen threads. The second half is my own assessment. Herdr happens to fill the one empty cell in my harness table, which is observability, and the five places I could put it are a two pane setup with Claude Code writing and Codex reviewing, one workspace per project for three projects, SSH reattach to NanoClaw on the Raspberry Pi, letting an agent use the socket API to wait for another agent to get blocked, and the old Omarchy machine at the hospital. It ends with three reasons not to rush.

herdr tmux terminal-multiplexer
141 views

Latest Slides

View all slides
AI 把寫程式變便宜了,那開發者還剩下什麼? 30 pages

AI 把寫程式變便宜了,那開發者還剩下什麼?

這一兩年我們都看到了,AI 讓寫程式這件事變得很便宜。但是便宜的東西不會是瓶頸,瓶頸只會往貴的地方移動。所以問題不是「AI 會不會取代開發者」,而是「當寫程式不再是門檻,開發者真正的價值在哪裡」。 不談特定框架、不推任何工具,只談一件事:軟體從來就不只是程式碼。決定要做什麼、決定不做什麼、驗證它能不能上線、出事的時候誰扛責任、那些沒被寫進 repo 的上下文、以及該放手讓 AI 跑還是該親自把關的臨界判斷,這些貴的部分,才是 AI 之後真正決定成敗的地方。 我會用自己一個人把構想送進正式環境的實際經驗,包括在醫院這種不能出錯的場域裡,怎麼判斷哪裡可以全交給 AI、哪裡必須人在迴圈。你會帶走一份可以馬上對照自己專案的判斷力清單,而不是又一個「AI 很厲害」的示範

iThome HWDC 2026 144